Closed
Bug 334908
Opened 20 years ago
Closed 11 years ago
trunk crashes [@ ReflowEvent::HandleEvent]
Categories
(Core :: Layout, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: dbaron, Unassigned)
References
()
Details
(Whiteboard: [needs retesting on Windows with WMV plugin])
Attachments
(1 file)
|
71.44 KB,
text/plain
|
Details |
There #1 unsolved trunk topcrash is crashes at ReflowEvent::HandleEvent:
http://talkback-public.mozilla.org/search/start.jsp?search=1&searchby=stacksig&match=contains&searchfor=ReflowEvent::HandleEvent&vendor=MozillaOrg&product=FirefoxTrunk&platform=All&buildid=&sdate=&stime=&edate=&etime=&sortby=bbid
Talkback provides almost nothing useful here, but getting a bug on file. I don't *think* this is the same as bug 334905, but it is a possibility.
Comment 1•20 years ago
|
||
*** Bug 335701 has been marked as a duplicate of this bug. ***
Comment 2•20 years ago
|
||
Latest Trunk, clean profile.
1. Start Firefox.
2. Open new Tab.
3. Visit URL http://www.totgelacht.com/html/212.htm.
4. Close Tab.
Result: Firefox crashes.
Comment 3•20 years ago
|
||
I am seeing this on my machine as well here. I grabbed the crash info from dep-walker. Maybe that will expound on it a little bit more than the stack is (or isn't).
Comment 4•20 years ago
|
||
Comment 5•16 years ago
|
||
Comment 0 speaks of a topcrash at ReflowEvent::HandleEvent. There were no crashes there in the last week. I don't think the function even exists now.
Comment 2 is a site that uses the WMV plugin. That should be retested.
Comment 4 is a syscall log. I think those are rarely useful for Firefox bugs.
If the URL in comment 2 no longer crashes, it's safe to mark this bug as WFM.
Whiteboard: [needs retesting on Windows with WMV plugin]
Comment 6•11 years ago
|
||
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WORKSFORME
Updated•8 years ago
|
Product: Core → Core Graveyard
| Assignee | ||
Updated•8 years ago
|
Component: Layout: Misc Code → Layout
Product: Core Graveyard → Core
You need to log in
before you can comment on or make changes to this bug.
Description
•