RuntimeError: The Tribler core has unexpectedly finished with exit code -1073740791 and status: 1!

[sentry-for-tribler]

Sentry Issue: TRIBLER-8R

CreationTraceback: 
  File "src\run_tribler.py", line 213, in <module>
  File "src\tribler-gui\tribler_gui\utilities.py", line 395, in trackback_wrapper
  File "src\tribler-gui\tribler_gui\core_manager.py", line 97, in on_request_error
  File "src\tribler-gui\tribler_gui\core_manager.py", line 177, in start_tribler_core

RuntimeError: The Tribler core has unexpectedly finished with exit code -1073740791 and status: 1!

[PID:10684] 2021-10-01 02:01:05,384 - ERROR <community:651> TriblerTunnelCommunity.on_packet_from_circuit(): Exception occurred while handling packet!
Traceback (most recent call last):
  File "ipv8\messaging\anonymization\community.py", line 647, in on_packet_from_circuit
  File "ipv8\messaging\anonymization\community.py", line 42, in wrapper
  File "ipv8\messaging\anonymization\community.py", line 727, in on_creat...
  File "src\tribler-gui\tribler_gui\utilities.py", line 398, in trackback_wrapper
  File "src\tribler-gui\tribler_gui\utilities.py", line 395, in trackback_wrapper
  File "src\tribler-gui\tribler_gui\core_manager.py", line 87, in on_core_finished

[ichorid]

@qstokkink , is it you testing Tribler/py-ipv8#1044 ?

[qstokkink]

Nope, not me. Looks like a duplicate of #4880, also #5856.

[devos50]

This issue might actually be hard to debug since the included traceback ("Exception occurred while handling packet") should not make Tribler crash. The core manager simply keeps track of the latest Traceback it notices in the logs and also triggers on non-critical exceptions.

The exit code -1073740791 corresponds to 0xC0000409 which corresponds to a STATUS_STACK_BUFFER_OVERRUN exception (also see here). Maybe it's caused by a library that we are using? 🤔

[drew2a]

Let's close the issue regarding the low count of these errors (reported just one time just by one user)

and @devos50

This issue might actually be hard to debug since the included traceback ("Exception occurred while handling packet") should not make Tribler crash.

and @qstokkink

Looks like a duplicate of #4880, also #5856.