Closed
Bug 154415
Opened 23 years ago
Closed 23 years ago
Opening MLB.com in tab after WSj.com crashes browser
Categories
(Camino Graveyard :: General, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: pettit, Assigned: mikepinkerton)
References
(
URL
)
Details
(Keywords: crash, stackwanted)
Attachments
(2 files)
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Macintosh; U; Darwin Power Macintosh; en-US; rv:1.0.0)
Gecko/20020606
BuildID: Chimera v .3
If you go to wsj.com and then use the keyboard to open a new tab, then go to
mlb.com the browser crashes immediately.
Reproducible: Always
Steps to Reproduce:
1.open www.wsj.com
2.Use keyboard to open a new tabbed window
3.open www.mlb.com in the new tabbed window
Actual Results: browser crashes.
WorksForMe using Chimera/20020625. Robert, can you still reproduce this crash
using a more recent Chimera nightly? If so, please attach a crash report.
Changing Product to Chimera.
Assignee: Matti → saari
Component: Browser-General → General
Keywords: crash,
stackwanted
Product: Browser → Chimera
QA Contact: imajes-qa → winnie
Version: other → unspecified
Comment 2•23 years ago
|
||
I can crash this based on the steps provided. Tested with 2002-06-28-05 NB.
Stack trace coming.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Comment 3•23 years ago
|
||
Comment 4•23 years ago
|
||
we need to see if this happens in mozilla, or if it has been fixed already and
we should pick up that fix
Assignee: saari → pinkerton
| Assignee | ||
Comment 5•23 years ago
|
||
i can't repro this with a build from 7/24 (debug)
| Assignee | ||
Comment 6•23 years ago
|
||
can't repro with my opt build either. petersen? can you?
Comment 7•23 years ago
|
||
Hmm. I was able to reproduce the crash based on the steps on first try (not sure
what build was running at the time). However, I can't get it to crash again with
these same steps using (2002-07-24-05). I deleted my cache for good measure and
tried it again with no success in crashing the application.
Comment 8•23 years ago
|
||
I tried to repro this bug:
- 07-24 build: couldn't repro
- 06-24 build (first try): crashed with a similar stack as the one that
petersen attached in comment #3. will attach this stack later.
- 06-24 build (second try): couldn't repro
not 100% reproducible, and doesn't look reproducible at all with the current
build. maybe it got fixed with some patch checked in over the past month...
Comment 9•23 years ago
|
||
| Assignee | ||
Comment 10•23 years ago
|
||
ok, wfm then. reporter, if you see this with nightly builds after 7/24, please
reopen.
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•