[WIP] Handling Crashes of Psychopy Subprocess #8
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Coding agent has begun work on Handling Crashes of Psychopy Subprocess and will replace this description as work progresses.
See problem context
TITLE: Handling Crashes of Psychopy Subprocess
USER INTENT: The user aims to investigate and resolve issues related to the handling of crashes or unexpected terminations of the Psychopy subprocess, specifically addressing lag in the mesofield and mouse input, as well as the creation of zombie processes.
TASK DESCRIPTION: The user requires a solution to ensure that when the Psychopy subprocess crashes, it does not cause lag in the mesofield or mouse input, and that any zombie processes created by the crashed subprocess are properly handled and cleaned up.
EXISTING: The user has identified the problem with the current handling of the Psychopy subprocess but has not provided specific code or file paths related to the implementation.
PENDING: The user needs a solution that effectively manages the subprocess's lifecycle, including proper error handling and cleanup of resources when the subprocess crashes.
CODE STATE: No specific files or code snippets have been provided yet, as the user is in the initial stages of discussing the problem.
RELEVANT CODE/DOCUMENTATION SNIPPETS: None provided at this stage.
OTHER NOTES: The user is focused on improving the robustness of the application by addressing subprocess management issues, which may involve implementing better error handling and resource cleanup strategies.