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 was archived by the owner on Aug 9, 2018. It is now read-only.
Whenever the exception handler hits and we return an error to the client the server usually segfaults shortly afterwards.
Current best theory is that we're double-disposing the angularcontext object. Ideally angularcontext would protect itself against this by remembering that it's disposed and treating duplicate calls as no-ops.
The text was updated successfully, but these errors were encountered:
Whenever the exception handler hits and we return an error to the client the server usually segfaults shortly afterwards.
Current best theory is that we're double-disposing the angularcontext object. Ideally angularcontext would protect itself against this by remembering that it's disposed and treating duplicate calls as no-ops.
The text was updated successfully, but these errors were encountered: