You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 4, 2021. It is now read-only.
The code before would hold the lock while exiting, thus forcing the continuation to run under the lock. This ended up causing Exit tasks to be chained on the same stack frame, ending up in a stack overflow for solutions which queued a lot of builders.
Fixes#3649
The code before would hold the lock while exiting, thus forcing the continuation to run under the lock. This ended up causing Exit tasks to be chained on the same stack frame, ending up in a stack overflow for solutions which queued a lot of builders.
Fixes#3649
…#3660)
The code before would hold the lock while exiting, thus forcing the continuation to run under the lock. This ended up causing Exit tasks to be chained on the same stack frame, ending up in a stack overflow for solutions which queued a lot of builders.
Fixes#3649
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
the issue started last week, as the first 7.4 version hit the alpha channel.
there's no valuable info in the logs at all, it just hangs... forever.
The text was updated successfully, but these errors were encountered: