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
Avoid a %crun crash #19185
Labels
Milestone
Comments
Branch: public/19185 |
Commit: |
Branch pushed to git repo; I updated commit sha1. This was a forced push. New commits:
|
comment:3
ok, bot is happy and this looks good enough |
comment:4
Thanks! |
comment:5
Reviewer name missing |
Reviewer: Frédéric Chapoton |
Changed branch from public/19185 to |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When typing several times in a row the following command (which is indeed incorrect)
Sage ends up crashing. That's apparently because the timer is started but not stopped (because of the exception).
This very small branch fixes the problem, and may possibly also fix the other occurrences of a crash due to this function. It happens from time to time on my computer, though the previous example at least is deterministic.
I do not know how exactly I should doctest it, though.
CC: @vbraun @simon-king-jena
Component: performance
Author: Nathann Cohen
Branch/Commit:
28dd224
Reviewer: Frédéric Chapoton
Issue created by migration from https://trac.sagemath.org/ticket/19185
The text was updated successfully, but these errors were encountered: