To reproduce this bug you must have error pages (as opposed to dialogs) turned on. put pref("browser.xul.error_pages.enabled", true); in all.js or user.js. (see bug 28586) Visit a site that does not exist such as http://aosuthaoeusthaouesth.com/ See that an error page is presented. Type another location into the url bar or visit the search link. Press the back button. Actual result: crash Expected result: Error page is redisplayed. (Found on the lates nightly Linux build: 2002071121)

It isn't a regression since error pages are not enabled by default. I'm trying to reproduce the problem now, but it didn't affect a build I had done last night. I might dupe this against bug 157004

Re: Additional Comment #1 From Adam Lock 2002-07-12 07:55 ------- > It isn't a regression since error pages are not enabled by default. My bad. I misread the bug description and though this problem would have been caused by your checkin and appear even when error pages are disabled.

Stack trace, Stephen?

Mozilla prints out the following on stdout as it crashes: INTERNAL ERROR on Browser End: Exec of "java_vm" failed: 2 < System error?:: No such file or directory Gdk-ERROR **: Fatal IO error 9 (Bad file descriptor) on X server :0.0. INTERNAL ERROR on Browser End: Could not read ack from browser System error?:: Resource temporarily unavailable

Based on that message I tried removing libjavaplugin_oji.so from my plugins directory. When that file is removed, I no longer get the crash. I'm not sure why java would be invoked at that point.

I checked in a fix for bug 157004 so the error page shouldn't appear in session history anymore. Marking fixed.

*** Bug 167593 has been marked as a duplicate of this bug. ***