Closed Bug 140544 Opened 23 years ago Closed 22 years ago

Website causes application error terminating Mozilla

Categories

(SeaMonkey :: General, defect)

Product:
SeaMonkey
Component:
General
Platform:
x86
Windows 2000
Type:
defect
Priority:
Not set
Severity:
critical

Tracking

(Not tracked)

Status:
RESOLVED DUPLICATE of bug 160602

People

(Reporter: webnut4, Assigned: Matti)

References

(
URL
)

Details

(Keywords: crash, testcase)

Attachments

(2 files)

Javascript code which crashes mozilla
243 bytes, text/html
Details
same testcase without the strict Javascript warnings
251 bytes, text/html
Details
From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.9+) Gecko/20020426 BuildID: 2002042608 On this and at least one other page, I am seeing a total crash of the browser which I haven't had any problem with on prior builds for at least many weeks. The crash occurs after a significant amount of the page is already loaded but not displayed yet. Reproducible: Always Steps to Reproduce: 1.Go to www.washingtonpost.com 2.It will crash. 3. Actual Results: Error says "The instruction at "0x77f82dd2" referenced memory at "0x39393929". The memory could not be "read". Click on OK to terminate the program
worksforme with Linux build 20020426
I can confirm this, build 2002042703, Windows 2000. This happens with many webpages, making the browser unusable. Also breaks on freshmeat.net, slashdot.org. No talkback generated.
wfm with win2k build 20020427.. Reporter: Can you add a talkback ID to this bug ?
wfm (2002042606, win2k)
This crash doesn't produce talkback. Is that a bug in itself? I wasn't sure if the nightly installer build had talkback enabled, so I manually downloaded the nightly win32 talkback build, 2002042708 (no installer), and it does the same thing. Same crash message, every time, no talkback. I tried uninstalling and removing the mozilla directory, then reinstalling, no effect. I've tried modern and classic themes, always crashes. I use large fonts and put them back to normal sized fonts, still crashes. I don't know what's different about my install that makes it crash... This is a new crash which I first noticed with yesterday's (4/26) build, but it may have happened within the last week or so. Any other ideas for things I can try to isolate it?
My browser doesn't crash (1.0RC1 on Linux), but maybe the crash has to do with the fact that somehow the site manages to open a popup window, even though I have popups disabled.
WFM. Build ID: 2002-04-25-10. Windows 2000.
Apparently it has something to do with Javascript. I've pruned the slashdot webpage down to this attachment.
wfm: both saving the attachment as a local file and also viewing the attachment in mozilla. Win2k 1.0 nightly 2002-04-27-06. slashdot and washingtonpost.com also wfm.
Maybe the original poster can confirm with the above attachment? Anyway, I am going through the ordeal of downloading the source and tools and building so I can try to run it in the debugger since no one can seem to reproduce this but me. Hopefully I will have some info in the next couple of days.
Sorry for my late followup to this bug report. I have tried the 2002042708 build now and I am getting crashed just the same as my original report. It sounds like Hal is experiencing the exact same crash. Also, I tried his javascript code attachment which causes the very same type problem for me. I am getting no talkback ID, the browser just instantly closes, terminating itself from memory.
Okay, I was finally able to get mozilla downloaded and installed. Here is what happens with today's source out of CVS: I compile with MOZ_DEBUG undefined (debug disabled) - I still get the crash. I get this error: Unhandled exception in mozilla.exe: 0xC0000005: Access Violation I compile with MOZ_DEBUG=1 (debug enabled) to track this thing down, an LO AND BEHOLD - IT WORKS! I don't get the crash in debug mode! Build 2002050108 also crashes with symptoms described in earlier comments, btw. I would like to isolate this further. This bug is really bugging me. Can anyone give me some suggestions for other things I can try?
I created a new profile and didn't modify it at all. It still crashes. When turning of javascript for navagator, I don't get this crash. It's definately javascript related.
can you get a stacktrace out of the non-debug build?
Yes, here is the stacktrace: NTDLL! 77f83b27() NTDLL! 77f83bae() NTDLL! 77f82f0b() XPCOM! 10033c78() 03670488() XPCOM! 1000b862() f18b5608()
Another piece of data - if you've been browsing a while and the Java debug console comes up, then you can turn on javascript and it works fine.
Note: in the debug build, I get the following warnings. Is it possible that these can cause a crash in certain conditions? Document http://bugzilla.mozilla.org/show_bug.cgi?id=140544 loaded successfully JavaScript strict warning: http://bugzilla.mozilla.org/attachment.cgi?id=81313&action=view line 6: assignme nt to undeclared variable now JavaScript strict warning: http://bugzilla.mozilla.org/attachment.cgi?id=81313&action=view line 7: assignme nt to undeclared variable tail Document http://bugzilla.mozilla.org/attachment.cgi?id=81313&action=view loaded successfully
This bug still crashes me when I go to www.washingtonpost.com and a couple other sites and forces me to stay away from the more highly featured builds which is quite disappointing. Wish someone could work this one out.
attachment 87315 [details] also crashes mozilla for me. Oh well, it was a theory.
My problem with Mozilla crashing on washingtonpost.com has been narrowed down. For me, it is only happening when I run Macro Express 3 at the same time. Of course, I always had this program running and I didn't suspect that any of my utilities could be interfering with Mozilla.
Ah-ha, that is a good find. I have found that my mozilla problem only happens when JS pager virtual desktop is running. You can get it here: http://hem.fyristorg.com/jspage/
I too am having this problem, but on the site: http://baseball.espn.go.com/mlb/index Mozilla crashes with no talkback, but only when JS Pager is running. However, I have also found out that the crash only happens when JS Pager has the "System menu - Send to desktop (x,y)" option turned on. If this option is disabled, Mozilla exists happily with JS Pager. Note: Mozilla1.0 did not have this problem. It started this behavior with 1.1alpha.
When I go to http://baseball.espn.go.com/mlb/index I also experience the crash. The error is the following: The instruction at "0x77f82dd2" referenced memory at "0x39393929". The memory could not be "read". Click on OK to terminate the program. Also, www.cnet.com does the same thing. Once again, in my case the conflict is with Macro Express 3.0d.
Does Macro Express 3.0d add anything to the system menu? The "System menu - Send to desktop (x,y)" option in JS Pager adds an item to the system menu. Mozilla crashes on several sites when the extra system menu item is present. If Macro Express also adds items to the system menu, then I would say we have the problem isolated.
Macro Express 3 doesn't seem to add anything to the System menu. It is a very full-featured utility however, probably as complicated as any. Maybe if someone else can try it out and confirm the problem while I try out JS pager....
Note the report in bug 160602 is very similar to this bug, and may in fact be a duplicate. It also involves a crash that produces no Talkback report. The alert from the Windows OS reported there, and in the duplicate bug 161574, is "instruction at 0x77f83cab referenced memory at 0x39393929"
Contributors in bug 160602 have reported that simply entering this javascript:URL and hitting <Enter> can crash Mozilla with the same address violation as reported above. Could contributors here give it a try and see what happens - thanks javascript: (new Date()).getTime();
Yes, same crash... Note, this is only with JS pager on that I get this crash. Otherwise, no problems. Here's the stacktrace I get when running with build 2002071608 and using that javascript URL: NTDLL! 77f8e59a() NTDLL! 77f8edc6() NTDLL! 77f848a5() XPCOM! 60eb1928() 02ba30c8() XPCOM! 60e89a75() f18b5608() I download/compile/debug with newer versions if there's something you'd like to try. This is fairly reliably reproducable...
OK, thanks! I'm going to go ahead and dupe this bug against bug 160602, since there are more entries there. I will make sure everyone on this bug is cc'ed on the other bug as well - thanks to all! *** This bug has been marked as a duplicate of 160602 ***
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
Same crash for me, but only when JS Pager adds "Send to Desktop (x,y)" in the System menu. If I configure JS Pager to not add this to the system menu, Mozilla functions normally and does not crash.
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: