-
Notifications
You must be signed in to change notification settings - Fork 25
Traceback from exceptions accumulates on REPL on 4.1.0 #28
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
Comments
This seemed fairly harmless in REPL. Is it definitely REPL only? If not, is there any chance of leaking memory for applications with repeatedly/many caught exceptions? I'd guess not as the Traceback/text would only be prepared when it's not caught? |
I assume it's REPL because it's the only case where an exception doesn't cause a VM reset. However, I haven't looked in detail yet so I may be wrong. |
This is due to the MIDI library reusing ValueError: https://github.com/adafruit/Adafruit_CircuitPython_MIDI/blob/master/adafruit_midi/midi_message.py#L108-L109 I'll move this issue to the midi repo. Instead, it should create a new exception each time. |
I just caught all exceptions including |
Please try absolute latest and file a new issue if the problem persists. |
Observed on
4.1.0-rc.1
and briefly discussed on Discord.4.1.0
has same issue with accumulation of stack trace stuff inTraceback
output:The text was updated successfully, but these errors were encountered: