-
Notifications
You must be signed in to change notification settings - Fork 452
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
RuntimeError: Access violation - no RTTI data! #7886
Comments
def _task_process_alerts(self):
for hops, ltsession in list(self.ltsessions.items()):
if ltsession:
for alert in ltsession.pop_alerts(): # error has been raised here
self.process_alert(alert, hops=hops) RTTI = Run Time Type Information. pop_alerts documentation: https://libtorrent.org/reference-Session.html#pop_alerts()
A user has removed a torrent just before the crash:
So, I can identify two probable causes of the error:
def _task_process_alerts(self):
for hops, ltsession in list(self.ltsessions.items()): # <- here
... |
I couldn't find a way to properly fix the error besides addressing it through #7940, which fixes potentially dangerous situations but is not the root cause of the original issue. Therefore, I'm unassigning myself from it. |
This issue has not seen activity for 60 days. It is now marked as stale. Please provide additional information or this issue may be closed in the future. We value your contribution and would love to hear more! |
I cannot reproduce this error. If an error is raised in this location, it is only logged without crashing. ERROR:DownloadManager:Task resulted in error: Access violation - no RTTI data!
Traceback (most recent call last):
File "ipv8\taskmanager.py", line 153, in done_cb
future.result()
File "ipv8\taskmanager.py", line 28, in interval_runner
await task(*args)
File "ipv8\util.py", line 53, in call_async
return func(*args, **kwargs)
File "tribler\core\libtorrent\download_manager\download_manager.py", line 604, in _task_process_alerts
raise RuntimeError("Access violation - no RTTI data!")
RuntimeError: Access violation - no RTTI data! Apparently, this has already been fixed. |
Sentry Issue: TRIBLER-1JG
The text was updated successfully, but these errors were encountered: