In LiveDebugger we are tracing LiveView processes and when there is a crash or navigate, then the process dies and new one is taking its place. In 0.4.0 we’ve improved the system of finding “successor” process and it should give you overall a better experience.
Regarding debugging endless loops remember that you can open LiveDebugger in a separate window (port defaults to 4007 so it should be localhost:4007). Nevertheless if the reloads are fast then the ActiveLiveViews page is also reloading since the refresh is triggered on new LiveView process being born.
We will look more into “endless crash reload” debugging and how to improve it.
Thank you for your feedback
