Closed Bug 302537 Opened 19 years ago Closed 19 years ago

Upon entering some web pages, this error message suddenly appears and closes the page, sending me back to the start page: "Mozilla.exe has generated errors and will be closed by Windows; You will need to restart the program; An error log is being creat...

Categories

(SeaMonkey :: General, defect)

x86
Windows 2000
defect
Not set
major

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: dcurtis1, Unassigned)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8b2) Gecko/20050702
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8b2) Gecko/20050702

Mozilla shuts down upon attempting to enter certain web pages.  The following 
error message is generated about 20 seconds before it shuts down:

"Mozilla.exe has generated errors and will be closed by Windows. You will need
to restart the program.  An error log is being created."  Nearly 3 out of every
10 web pages prompt the error message.

Reproducible: Sometimes

Steps to Reproduce:
1.While searching in Google, I first click on a link.
2.This takes me to a web page.
3.I get the aforementioned error message sometimes, and Mozilla shuts down.

Actual Results:  
Ultimately, Mozilla shuts down, forcing me to start my search again.

Expected Results:  
Mozilla should have permitted me access to the page if it had been safe to do
so.  Or, at the very least, the software should have forced me to return to the
previous page instead of shutting down altogether.

There is an additional problem.  When I click on the Mozilla icon on my desktop
to open Mozilla, I get this message every time: "The file/res/hiddenWindow.html
cannot be found.  Please check the location and try again."  This suggests to me
that a specific file is missing. Perhaps another program erased it or wrote over it.
(In reply to comment #0)
> There is an additional problem.  When I click on the Mozilla icon on my desktop
> to open Mozilla, I get this message every time: "The file/res/hiddenWindow.html
> cannot be found.  Please check the location and try again."

This issue is fixed. Please try a newer Seamonkey 1.0a (Mozilla 1.8b4) trunk
build from 
http://ftp.eu.mozilla.org/pub/mozilla.org/seamonkey/nightly/latest-trunk/
and install it with Talkback please.

Have you installed the Talkback (Quality Feedback Agent)? Comes TB up if you
crash? Can provide some TB ids for crash reports?

Summary: sending me back to the start page: "Mozilla.exe has generated errors and will be closed by Windows; You will need to restart the program; An error log is being created." Is there a problem with the web page or is there a problem with Mozilla? → sending me back to the start page: "Mozilla.exe has generated errors and will be closed by Windows; You will need to restart the program; An error log is being created."
Version: unspecified → Trunk
This is an unusually high crash rate. Talkback traces would help. Do you have
any extensions or plugins installed? Those might be conflicting with each other.

Failing talkback traces, the address of pages you consistently crash on would be
a minimum to turn this into a valid bug. As it is there's not enough detail to
go on here, no one else is seeing that high a random crash rate.

You don't have roboform installed, do you? That's been crashing people like
crazy lately, try removing it. Try removing all your extensions for a bit and
see if that helps. if it does add them back one by one and see if you can figure
out which one is causing the conflict.

Feel free to reopen if you can supply more detail.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → INVALID
The original summary for this bug was longer than 255 characters, and so it was truncated when Bugzilla was upgraded. The original summary was:

Upon entering some web pages, this error message suddenly appears and closes the page, sending me back to the start page: "Mozilla.exe has generated errors and will be closed by Windows; You will need to restart the program; An error log is being created."
You need to log in before you can comment on or make changes to this bug.