Pale Moon (28.5.0, 32-bit, Windows 7) hanging/crashing after a few hours. Has been doing this for a few versions.

[Tharthan]

I see.

I didn't understand the instructions because I didn't know if you meant that I was somehow supposed to follow them from within Pale Moon itself, or from somewhere else.

I didn't have on my computer (nor had I heard of) "Process Explorer", so I had to download it.

Ought I to use the 64-bit version (in the ZIP), or the other one (presumably 32-bit, also in the ZIP)? I ask this because I was wondering if it would matter since my installation of Pale Moon is 32-bit. Or since this is a general program, would the 64-bit version be better since my Windows 7 OS is 64-bit?

[satrow]

Use the x64 version Run as Administrator.

PE_View_dlls.jpg

[Tharthan]

Ixnay on the LLDay.

What next?

[satrow]

Ixnay on the LLDay.

What next?

A translation?

If there's no trace of the WL .dll, use Pale Moon as you would normally and let us know if it still hangs/freezes, collect/upload fresh data if do.

[Tharthan]

A translation?

You're not familiar with Pig Latin? It's a sort of wordgame-esque thing that is well-known in English speaking countries.

I was trying to be somewhat jocular-

"Nix [https://en.oxforddictionaries.com/definition/nix] on the DLL" (although "ixnay" [https://en.oxforddictionaries.com/definition/ixnay] and "amscray" [https://en.oxforddictionaries.com/definition/us/amscray] have entered standard English as colloquial words)

If there's no trace of the WL .dll, use Pale Moon as you would normally and let us know if it still hangs/freezes, collect/upload fresh data if do.

Will do.

Do you want AppCrashView information if the browser continues to hang/crash, because the WinDbg approach doesn't seem to be effective for me, considering that I can't seem to artificially recreate the exact crash conditions intentionally.