How to debug slowness

[Moonchild]

That unloads it, I meant something in the style of Edge's sleeping tabs. They wouldn't need to be reloaded when switching back to a sleeping tab. So a bit like suspending the browser process, just on a tab basis.

That's not possible for us. Edge can do this by juggling their content processes, but tabs in Pale Moon are all part of the same application process, which cannot be put "to sleep" without impacting all tabs.

[UCyborg]

I assumed you could tell tabs' contexts apart somehow and just skip their processing if desired.

[Moonchild]

In a limited fashion, we can. And we already do so, e.g. by clamping timers for background tabs. But as I already hinted at before, modern web "features" detach processing from specific documents/contexts which, by necessity, use pool structures. So, while potentially an option, it will not be anywhere near as trivial as a separate process would make it.

Also, at most this would be beneficial for memory use the way Edge does it, and not in terms of processing speed...

[xtal256]

It sounds like this ghost window problem is the main cause of slowness, but I still like to know more about what's going on "under the hood" when a problem occurs. When the Pale Moon process goes to 100% I often bring up Process Hacker / System Informer and look at the stack trace, but all that can really tell me is what module the execution is currently in. Would I be able to download debugging symbols to see the exact function calls, or would I also need a debug build for that?