Check and stop an unwanted spark profiler session
A staff member may start a profile and lose its console output or leave before the test finishes. Check the profiler state before starting another recording. Spark provides controls for inspecting and ending a session, so a server restart is not the first response.
Record the starting point
Find out who requested the capture and what event it was intended to include. Record the current symptom and approximate start time. Use the command prefix appropriate to the platform; a proxy's profiler is not automatically the same session as its backend's profiler.
Work through the change
- Check installed command help and run the documented profiler information command, such as
/spark profiler info. Confirm the component and active recording details. - If the required event has been captured, stop the session using the normal profiler stop command. Use the supported local save option if the report needs privacy review before upload.
- If the recording is unwanted or contains no useful test, use the documented profiler cancel control rather than killing the Minecraft process.
- Check profiler information again and note the outcome. If another capture is needed, start a new bounded session with an explicit timeout and named test action.
Check the result
There should be one understood recording state and, when saved, a known report location. Share the result with the staff member who requested it. Record a cancelled session as cancelled rather than presenting it as a successful performance capture.
If the result differs
If commands affect no session, confirm whether you are on the proxy, server or client platform and using its correct prefix. If an upload hangs, separate report delivery from the recording state. Repeatedly starting new profiles can make that distinction harder.
Do not restart the service solely to clear an uncertain profiler state. Preserve relevant console output and ask support about a reproducible control failure. Revert only diagnostic settings changed for the abandoned test, leaving worlds and plugin data intact.