-
-
Notifications
You must be signed in to change notification settings - Fork 26
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
Nested signal handling leads to excessive slowdown of sig_occurred()
#215
Comments
I guess recursive That said, is there any cleaner way than the current (fragile) method of using reference counting and run the garbage collector? It looks like it will only be a matter of time until someone comes across a case where the garbage collector is run too many times consecutively which leads to unexplained slowdown. |
Actually nested signal handling is not needed, you might as well do something more innocuous such as
But |
How about we throttle the garbage collector to run at most e.g. 10% of the (wall) time? That way, worst case something heavy is done in a place where |
From sagemath/sage#39224
SageMath session:
Note the invocation of
g()
that is marked# slow
.The text was updated successfully, but these errors were encountered: