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.
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.