32.2.0 Crash on MP4 in Windows 7

Users and developers helping users with generic and technical Pale Moon issues on all operating systems.

Moderator: trava90

Forum rules
This board is for technical/general usage questions and troubleshooting for the Pale Moon browser only.
Technical issues and questions not related to the Pale Moon browser should be posted in other boards!
Please keep off-topic and general discussion out of this board, thank you!
User avatar
Knows the dark side
Knows the dark side
Posts: 4442
Joined: 2015-12-09, 15:45

Re: 32.2.0 Crash on MP4 in Windows 7

Unread post by moonbat » 2023-05-24, 01:05

andyprough wrote:
2023-05-24, 00:57
, and malware block lists similar to uBlock, among other things.
Which is why you look at the logs to see what was blocked, and unblock one by one & refresh the page to see if it fixes the problem. Then make an exception for that one item. It's how you troubleshoot any adblocker instead of blanket disabling it for that one site. Always pays to learn how these things work. For example, I have made global exceptions for embedded tweets or instagram posts so that I don't have to turn them on for every site that has them.
"One hosts to look them up, one DNS to find them and in the darkness BIND them."

Linux Mint 21 Xfce x64 on HP i5-5200 laptop, 12 GB RAM.
AutoPageColor|PermissionsPlus|PMPlayer|Pure URL|RecordRewind|TextFX

User avatar
Posts: 11
Joined: 2023-03-16, 13:21

Re: 32.2.0 Crash on MP4 in Windows 7

Unread post by Shadow » 2023-05-24, 11:29

From the NoScript dev...
The wording here ("Deprecated, obsolete and unsupported") says it all, I think.

I've got no resources to work on that code-base anymore, therefore it might or might not be unsafe to use and I couldn't even tell it.

Classic is as is forever unless some guru comes along and forks it or something.

I have gone ahead and unchecked clearclick, xss, and abe because I just decided too. I doubt they were doing much of anything anyway. Clearclick rarely showed and when it did it always got in the way like a false positive. Xss I haven't seen it nag in forever. Abe, don't really know what it does, maybe nagged once or twice in many years. I also changed entry noscript.injectionCheck to 0. I'm also thinking entry noscript.surrogate.enabled should be set to false as it looks old for present net but not sure entirely. Ghacks has an article on it.

I just thought I'd put out what I changed there. I guess I wanted to make it less advanced and more basic in hopes it helps plus the feeling it wasn't doing much.

Post Reply