Closed
Bug 784093
Opened 13 years ago
Closed 12 years ago
Creating 50 or so new blank tabs makes Firefox crash badly
Categories
(Core Graveyard :: Plug-ins, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: nicolas.barbulesco, Unassigned)
Details
(Keywords: crash)
Crash Data
Attachments
(1 file)
|
162.10 KB,
application/x-rar-compressed
|
Details |
Hello,
Win Vista, Firefox 14.0.1.
I was creating many blank Firefox tabs, in order to reproduce a little bug in Firefox — which I will not file, given my mood now. Oh, not 5000, about 50. But supposed to be *empty*.
And Firefox crashed badly. At restart, Firefox had lost almost all my tabs. He showed me the restore dialog, but with almost every window having zero tab — which is absurd. This is the bug 696684 I had encountered before on Firefox Mac.
I cannot rely on Firefox to keep my tabs, that's too bad.
Why do Chrome and Safari cleanly restore all my tabs after a crash, and Firefox can't do so reliably ?
On the other hand, only Firefox is capable of restoring my entered form contents.
Making Firefox crash-free, and, in case a crash occurs anyway, restore-reliable, would be great !
Thank you,
Nicolas
Comment 1•13 years ago
|
||
Please provide a crash ID if present. http://support.mozilla.org/en-US/kb/Mozilla%20Crash%20Reporter
Updated•13 years ago
|
Component: General → Untriaged
Updated•13 years ago
|
Keywords: crash,
stackwanted
| Reporter | ||
Comment 2•13 years ago
|
||
Here is my folder "Crash Reports" : see attachment to come.
The big bad crash is the crash before the last one.
| Reporter | ||
Comment 3•13 years ago
|
||
Comment 4•13 years ago
|
||
(In reply to Nicolas Barbulesco from comment #2)
> Here is my folder "Crash Reports" : see attachment to come.
We need a crash ID (bp-...) from about:crashes, not a binary file we can't read.
Comment 5•13 years ago
|
||
FWIW, the only submitted ID from the zipped Folder is bp-0d2e55ef-ad94-4301-adbf-11ff32120821 ([@ mozilla::plugins::PPluginInstanceParent::CallNPP_SetWindow(mozilla::plugins::NPRemoteWindow const&) ])
Updated•13 years ago
|
Attachment #653889 -
Attachment mime type: text/plain → application/x-rar-compressed
Updated•13 years ago
|
Status: UNCONFIRMED → NEW
Crash Signature: mozilla::plugins::PPluginInstanceParent::CallNPP_SetWindow(mozilla::plugins::NPRemoteWindow const&)
Ever confirmed: true
Updated•13 years ago
|
Crash Signature: mozilla::plugins::PPluginInstanceParent::CallNPP_SetWindow(mozilla::plugins::NPRemoteWindow const&) → [@ mozilla::plugins::PPluginInstanceParent::CallNPP_SetWindow(mozilla::plugins::NPRemoteWindow const&) ]
Component: Untriaged → Plug-ins
Keywords: stackwanted
Product: Firefox → Core
Version: unspecified → 14 Branch
| Reporter | ||
Comment 6•13 years ago
|
||
Here I give you the entries I see in "about:crashes" :
bp-7cc31c3c-4cb4-44c0-a378-fd4092120822
bp-0d2e55ef-ad94-4301-adbf-11ff32120821
54f48ae8-02d8-4f2a-82f5-94a19702c5dd
a7c4d189-c2d2-4103-88bc-5383a43df463
9f92f9fa-7ceb-4cd8-b837-3b94b042b5e7
eeb3ed90-3c3a-49ac-9f08-e3ca77c930cc
6f4140d6-50cf-47db-a4a3-c71796358bd9
86584557-053e-44e7-af5b-e82c02fdc12b
By the way, this list in "about:crashes" gives the time of sending instead of the time of the crash, this is weird, and that's why I have difficulties to correlate the listed crashes with the crashes I remember.
Thank you for investigating.
Nicolas
Comment 7•12 years ago
|
||
Nicolas does this still crash using newest firefox, in safe mode?
Flags: needinfo?(nicolas.barbulesco)
Whiteboard: [closeme 2014-02-15]
| Reporter | ||
Comment 8•12 years ago
|
||
(In reply to Wayne Mery (:wsmwk) from comment #7)
> Nicolas does this still crash using newest firefox, in safe mode?
In Firefox 26, on Win 7, I have created 428 empty tabs, and Firefox is fine. But I did this on a more powerful computer.
Flags: needinfo?(nicolas.barbulesco)
Comment 9•12 years ago
|
||
thanks
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
Whiteboard: [closeme 2014-02-15]
Updated•4 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•