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.
If the application creates any timeouts or intervals during rendering, these will often run after the page rendering is complete and the angularcontext is disposed, which inevitably leads to a segfault.
This is actually really a bug in angularcontext itself, since it should ensure that the dispose method cleans up all of the state of the context and doesn't leave resources dangling.
The text was updated successfully, but these errors were encountered:
If the application creates any timeouts or intervals during rendering, these will often run after the page rendering is complete and the angularcontext is disposed, which inevitably leads to a segfault.
This is actually really a bug in
angularcontext
itself, since it should ensure that thedispose
method cleans up all of the state of the context and doesn't leave resources dangling.The text was updated successfully, but these errors were encountered: