400486 - Opening www.avsforum.com crashes Seamonkey 1.1.5.

Status: RESOLVED INVALID

(SeaMonkey :: General, defect)

Description

[Kevin Hill]

User-Agent:       Mozilla/5.0 (OS/2; U; Warp 4.5; en-US; rv:1.8.1.8) Gecko/20071014 MultiZilla/1.8.3.3k SeaMonkey/1.1.5
Build Identifier: Mozilla/5.0 (OS/2; U; Warp 4.5; en-US; rv:1.8.1.8) Gecko/20071014 MultiZilla/1.8.3.3k SeaMonkey/1.1.5

No details beyond the summary.
I have to revert to an earlier version of Seamonkey.

Reproducible: Always

Steps to Reproduce:
1.type in http://www.avsformu.com
2.press enter
3.
Actual Results:  
Page begins to build and then Seamonkey closes down.

Expected Results:  
For the past several years, www.avsforum.com has worked well.

Comment 1

[Peter Weilbacher]

Kevin, do you have the Flash plugin installed? If so, please remove it for a test. In 90% of the cases sudden crashes on often visited webpages happen when they start to use Flash advertisement. As the OS/2 Flash plugin is strongly broken, removing the npswf*.dll files helps in most cases. Installing Flashblock from http://flashblock.mozdev.org/installation2.html should have the same effect.

FWIW I cannot reproduce the crash.

Comment 2

[Kevin Hill]

Peter,

Thanks for the quick reply.

Last night I downloaded your enhanced version of Seamonkey 1.1.5 and tried that.  As I have found with a couple of other versions, the enhanced version was more stable.  No problems with AVSForum.com.

Today, I removed the enhanced version and replaced it with the standard 1.1.5.  AVSForum loaded correctly today, however, after a while there was corruption with the displayed page and my machine locked up.  After rebooting, I removed the npswf* files and used Seamonkey without Flash for quite a while with no problems.

At this point, I assume the Flash files are the culprit.

You may be pleased that the enhanced version is OK with the Flash files.

Thanks very much for your help.

Comment 3

[Peter Weilbacher]

OK, this seems to be a Flash problem (even though I don't know why my enhanced builds should be any better), so I resolve this as invalid.