Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[7.13.3] CoreCrashedError on Linux with error code 4: Interrupted system call (Unterbrechung während des Betriebssystemaufrufs) #7948

Open
kozlovsky opened this issue Mar 27, 2024 · 2 comments

Comments

@kozlovsky
Copy link
Collaborator

tribler.gui.utilities.CreationTraceback: , 
  File "run_tribler.py", line 119, in <module>, 
  File "tribler/gui/start_gui.py", line 82, in run_gui, 
  File "tribler/gui/upgrade_manager.py", line 252, in on_worker_finished, 
  File "tribler/gui/utilities.py", line 439, in trackback_wrapper, 
  File "tribler/gui/core_manager.py", line 135, in start_tribler_core, 
The above exception was the direct cause of the following exception:, 
Traceback (most recent call last):, 
  File "tribler/gui/utilities.py", line 442, in trackback_wrapper, 
  File "tribler/gui/utilities.py", line 439, in trackback_wrapper, 
  File "tribler/gui/core_manager.py", line 315, in on_core_finished, 
tribler.gui.exceptions.CoreCrashedError: The Tribler core has unexpectedly finished with exit code 4 and status: 1., 
Error message: Unterbrechung während des Betriebssystemaufrufs

The Core process duration before the crash was 0:14:47, so the error wasn't during the Core startup.

What is the best way to handle this type of error?
Probably, GUI should just restart Core in case of such an error?

Copy link

Sentry issue: TRIBLER-1MF

@drew2a
Copy link
Collaborator

drew2a commented Apr 18, 2024

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants