[FIXED] HTML5 Page Hangs SeaMonkey, Loop, Memory Leak

[therube]

I believe this is a NoScript issue ...


HTML5 Page Hangs SeaMonkey, Loop, Memory Leak, high CPU usage (25% == 1 core of quad)

NoScript 2.1.0.4rc4
SeaMonkey 2.1, Mozilla/5.0 (Windows NT 6.1; rv:2.0.2pre) Gecko/20110504 Firefox/4.0.2pre SeaMonkey/2.1pre
Windows 7 x32

URL: http://www.youtube.com/watch_popup?v=6Q ... &vq=medium

Does not hang FF 4.0.1
Does not hang SeaMonkey without NoScript & manually enabling/disabling JavaScript (Edit | Preferences ...)

What I believe is happening is this dialog which appears once in FF, is repeatedly being written in SeaMonkey, effectively hanging & then eventually crashing SeaMonkey.

Code: Select all

Click here to visit our frequently asked questions about HTML5 video.
Save Video As...
About HTML5
Stereo Mode (change...)

Crash reports did not return meaningful data.
This I obtained from 'WhatIsHang' should it mean anything to you, http://pastebin.com/sXAeW2AK .

http://www.nirsoft.net/utils/what_is_hang.html



All NoScript settings are at defaults.

Basically all you need to do is load URL.

Most likely you will receive an unresponsive script warning.
If you cancel, your screen will show the above code - multiple times.
(In FF401, it will only display once.)
After that enable yahoo.com & ytimg.com.
Most likely you will get a message that the video has been removed.
Revoke Temporary Permissions.

At that point, most likely you will lock up, memory usage will continually increase, until you crash.


(View Image, if need to see full size)

[therube]

(Our accounting system at work, my father wrote code that opens temporary files. The temporary files open in a specific location. One day, on one particular computer any program that used these temporary files, hung. Locked up, had to kill. I find in the code, he opens these temporary files, numerically incrementing them if an existing one exists. So if it finds file1, it tries to create file2. If that exists, he creates file3 ... And he does this through a blanket ERR=. So if ERR=, loop to next increment & try again. What happened on this particular computer was that the specified file location was not available to it. So when it went through its file creation process, this generic ERR= code - which did catch the invalid location (as it also did a duplicate filename), just kept on incrementing the file count - to no limit, thereby hanging the app.)

[Giorgio Maone]

Please check latest development build, thanks.

[therube]

Looks like that's got it.
Thank you .