Closed
Bug 408787
Opened 17 years ago
Closed 17 years ago
Being able to kill a thread for an open tab thats causing firefox to hang
Categories
(Firefox :: Tabbed Browser, enhancement)
Tracking
()
RESOLVED
DUPLICATE
of bug 407117
People
(Reporter: jssenyange, Unassigned)
Details
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0; SLCC1; .NET CLR 2.0.50727; .NET CLR 3.0.04506) Build Identifier: 2.0.0.9 It would be cool to be able to kill a thread/tab that causing the whole firefox process not to respond(hang). A situation where you have a number of open tabs and one makes firefox stop responding, you kill the entire firefox process but with hope of restoring to the previous session when restarting the firefox process. However every time you restart the process the tab still makes browser not respond. Its quite annoying to start a new session and have to go through you entire history to open over 27 tabs. It would be cool if you could be able to kill a specific tab thread for example from another mozilla session though it would raise again other security concerns. Reproducible: Always Steps to Reproduce: 1. Open a tab having a script or a big pdf that will take time to display 2. Kill process 3. Restart firefox and restore session Actual Results: Keeps reopening the tab hence hanging again Expected Results: I should have an option of selection specific tabs/websites that i want restored where restoring session. Being able to kill a tab thats causing the browser not to respond
Comment 1•17 years ago
|
||
A Tab does not run in a single Thread, also a window does not run in it`s own Thread. But you describe to different things in your bug report, your summary means that firefox should be able to kill a hanging Tab/thread which is imposssible and your expected results are about session restore (btw: The component "Session restore" would be correct instead of your selected "Tabbed Browser") marking as dupe of bug 407117
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•