Closed
Bug 413779
Opened 18 years ago
Closed 18 years ago
open multiple tabs the firefox crash!
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: itamar, Unassigned)
References
()
Details
(Keywords: crash, stackwanted)
Attachments
(1 obsolete file)
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9b3pre) Gecko/2008011412 Fedora/3.0b3pre-0.beta2.10.nightly20080113.fc9 Minefield/3.0b3pre
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9b3pre) Gecko/2008011412 Fedora/3.0b3pre-0.beta2.10.nightly20080113.fc9 Minefield/3.0b3pre
open multiple tabs the firefox crash!
10 tabs for example.
Reproducible: Always
Steps to Reproduce:
1. http://www.caseirasbrasil.com
2. open 10 or more tabs
3. firefox crash
| Reporter | ||
Comment 1•18 years ago
|
||
firefox bug report
:-)
it's not a patch
Updated•18 years ago
|
Attachment #298851 -
Attachment is patch: false
Comment 2•18 years ago
|
||
Do you crash also in the Firefox safemode (http://kb.mozillazine.org/Safe_mode) ?
Please provide a Breakpad Id of that crash, the bug report itself is useless.
http://kb.mozillazine.org/Breakpad
| Reporter | ||
Comment 3•18 years ago
|
||
crashed in safe mode too.
please check if this attached file is the crash report
https://bugzilla.mozilla.org/attachment.cgi?id=298851
in my computer the directory
~/username>/.mozilla/firefox/Crash Reports/
doesn't exist
when I open multiple tabs, firefox start eating my cpu (95% used) and crashes
Comment 4•18 years ago
|
||
Severity change to critical por favor, per severity docs.
| Reporter | ||
Comment 5•18 years ago
|
||
my machine is a sempron 2800+ with 1 GB of memory running fedora 8 32 bits
Comment 6•18 years ago
|
||
Reporter, please change severity to critical if this is in fact a crash report.
ryan@back40design.com: please don't bother asking users to set severity. triagers will do that if there's something useful floating around.
this bug has what appears to be a breakpad thingy, but it's not in its processed form, and as such is mostly useless.
luser: is this attachment processable?
Comment 8•18 years ago
|
||
(In reply to comment #7)
> this bug has what appears to be a breakpad thingy, but it's not in its
> processed form, and as such is mostly useless.
doesn't that look more like a bug buddy report? The build id has Fedora stamped all over it to. Is someone making rpms of nightlies available now?
Itamar: where did you get the package/archive of Firefox from?
Severity: critical → normal
Attachment #298851 -
Attachment description: firefox bug report → fedora bug report
Attachment #298851 -
Attachment is obsolete: true
Keywords: stackwanted
Comment 9•18 years ago
|
||
Those gnome crash report things are worthless, I don't know why they do that. Unless, of course, you want to walk the stack by hand (including manually parsing the symbol files).
| Reporter | ||
Comment 10•18 years ago
|
||
(In reply to comment #8)
RPMS FROM KOJI
http://koji.fedoraproject.org/koji/
Comment 11•18 years ago
|
||
We accept only bug reports from original Mozilla.org builds or if you/we can reproduce this with an original build. We can't reproduce this and that's means you have to provide a Breakpad id from an original Mozilla.org build.
| Reporter | ||
Comment 12•18 years ago
|
||
I will try with mozilla.org and update this ticket as soon as possible.
please hold.
Comment 13•18 years ago
|
||
Itamar: in case you didn't already know, official nightly builds are available from http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/ . The latest build is easily accessible from the latest-trunk folder.
Do you still crash using original STR in current koji builds? Do you also crash with the official build? And if so please provide a breakpad report id (now available from about:crashes)
Comment 14•18 years ago
|
||
I'm going to mark this incomplete. Please feel free to reopen with a crash report from Breakpad / Mozilla Crash Reporter, or more specific steps to reproduce that allow QA to reproduce this specific issue. Thanks!
Status: UNCONFIRMED → RESOLVED
Closed: 18 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•