Closed Bug 524864 Opened 16 years ago Closed 16 years ago

pulldown AJAX menu crashes entire system

Categories

(Core :: General, defect)

x86
Linux
defect
Not set
critical

Tracking

()

RESOLVED INVALID

People

(Reporter: rigel, Unassigned)

Details

User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.0.14) Gecko/2009090217 Ubuntu/9.04 (jaunty) Firefox/3.0.14 Build Identifier: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.0.14) Gecko/2009090217 Ubuntu/9.04 (jaunty) Firefox/3.0.14 I have replicated this bug with the gecko-using version of the Epiphany browser, so I suspect the bug is in gecko. I can most reliably replicate the crash when I get a pulldown Subject:(typically subject, may also have happened with other fields but do not remember clearly) menu from the web "Lite" front end of a Microsoft Exchange 2007 server. If I do not switch vterms within the first second or so of a freeze, it is unrecoverable. I can sometimes catch it and switch to a text vterm, and then restart gdm. even when unrecoverable, the mouse still works. This happens on two separate machines with nvidia binary drivers (different versions), but I have not tested with the open source nv drivers. Reproducible: Always Steps to Reproduce: 1.begin new email in ms exchange 2007 server "lite" front end 2.start typing subject similar to previous subjects 3.crash Actual Results: System monitor halts. system crashes. Expected Results: allowed to select previous subject line
Firefox/gecko is a usermode application and can not crash the system or the X server and it*s a bug in the system and not Firefox if Gecko triggers such a bug in your OS or the X-Server. simple logic for every usermode application: If the system crashes or freezes it's the fault of the system If The X server crashes or freezes it's the fault of the X-Server If a usermode applicatiuon crashes or freezes it's in most cases the fault of the application (exceptions are for example plugins in a browser) marking invalid
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.