-
Notifications
You must be signed in to change notification settings - Fork 815
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
app._fatal_error never completes and ooms #3069
Comments
(just an additional note: for now my workaround is to override App._fatal_error in my inheriting app) |
Are you updating the UI from a thread (other than the main thread) ? |
Assuming stale. Will need more information to reopen. |
Don't forget to star the repository! Follow @textualizeio for Textual updates. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Have you checked closed issues? https://github.com/Textualize/textual/issues?q=is%3Aissue+is%3Aclosed
Please give a brief but clear explanation of the issue. If you can, include a complete working example that demonstrates the bug. Check it can run without modifications.
Using aarch64, textual 0.32, python 3.9 on raspbian, on a raspberery pi 4.
I cannot share a reproducer yet (happens in a closed project source).
I could not provide a reproducer yet, but the problem is an exception triggered by a timer callback which goes into _fatal_error (I can see via py-spy, stack trace below), and does not complete, the process is eventually terminated by the oom-killer (I'm running on linux aarch64 raspbian on a raspberry pi 4 with 2 GB of ram, app normally takes ~60 MB).
I will try to produce a reproducer, I acknowledge this issue may be closed without one, I hoped to provide some "this happens" hook for future lookers.
I propose there should be a way to avoid this expensive / potentially buggy flow for a simpler "traceback.print_exc" or even "just exit" policy, perhaps by an environment variable or some configurable parameter via the textual module at runtime.
Here is the stack trace
It will be helpful if you run the following command and paste the results:
(note - I ran it in a different window then the one producing the exception, under tmux, so the actual height is more like 60, width is correct approximately)
Feel free to add screenshots and / or videos. These can be very helpful!
The text was updated successfully, but these errors were encountered: