Closed
Bug 493422
Opened 15 years ago
Closed 15 years ago
When a webpage in a single tab/window stops responding, the whole app crashes.
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 516518
People
(Reporter: diedrsch, Unassigned)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; es-ES; rv:1.8.1.20) Gecko/20081217 Firefox/2.0.0.20 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; es-ES; rv:1.8.1.20) Gecko/20081217 Firefox/2.0.0.20 If a tab crashes, the whole application crashes. When I restart Firefox I can restore the tabs and windows, but all server sessions are lost, including: rapidshare/netload/despositfiles downloads, Mail Server Sessions. I am not a programmer, but I read somewhere in the Internet that the problem could be solved by assigning a separate memory process to each new tab. That way the Windows "End task" would apply only to the web page that has stopped responding, and the whole Firefox application (with my mail sessions and downloads) would go on without problems. Your browser is great, I hope you will continue with the development and improvement. Thank you very much for your attention, Diedrich Schultz. Reproducible: Always Steps to Reproduce: 1. Start a webmail session and begin writing a new mail. Start downloading a big file from rapidshare/megaupload/depositfiles/easy-share/netload. 2. Open lots of Firefox Windows, each with a lot of tabs, until some page makes the application crash. 3. Restart Firefox. You will find that the mail you were writing is lost because the session with the mail server is lost. The download manager can not resume the broken downloads. I cannot reproduce the fact "a web page makes the application crash". But I can tell that "when a web page in a single tab stops responding, the whole application crashes. All the server sessions and downloads get lost".
Comment 1•15 years ago
|
||
Is this the behavior Google Chrome got?
Reporter | ||
Comment 2•15 years ago
|
||
Jesper, thank you very much for your comment. I have just found out that other web browsers have already solved the problem I am experiencing: Google Chrome, Internet Explorer 8... And according to this web-page, http://barrapunto.com/article.pl?sid=09/05/13/0927249&from=rss Firefox is already working on a solution for the problem. I am going to change the status of my "Bug Report", because it is not technically a bug. It is an architechtural problem that will be corrected in future versions.
Comment 3•15 years ago
|
||
We are hoping to address this: https://wiki.mozilla.org/Content_Processes
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•