Closed
Bug 948259
Opened 12 years ago
Closed 11 years ago
Hard crash with variable hover display
Categories
(Core :: XUL, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: canuckistani, Unassigned)
References
Details
(Keywords: crash)
Crash Data
Attachments
(1 file)
2.13 MB,
video/mp4
|
Details |
This happened just after a variable pop-up was painted, here's the crash report:
https://crash-stats.mozilla.com/report/index/fea6bfc4-0c50-44f3-9d86-2a54d2131210
Comment 1•12 years ago
|
||
CCing some people who may have a clue about what happened.
Crash Signature: [@ nsViewManager::ProcessPendingUpdatesForView(nsView*, bool) ]
Keywords: crash
Comment 2•12 years ago
|
||
Maybe somewhat related to bug 946658.
Comment 3•12 years ago
|
||
I have no clue about this.
![]() |
||
Comment 4•12 years ago
|
||
More reports and a summary about their data can be found at https://crash-stats.mozilla.com/report/list?product=Firefox&signature=nsViewManager%3A%3AProcessPendingUpdatesForView%28nsView%2A%2C+bool%29
Comment 5•12 years ago
|
||
I've occasionally seen regions of <xul:panel> content disappearing (being replaced with empty white blobs), which might be related, but I don't have consistent steps to reproduce.
It sometimes happens when hovering "window" when paused inside the debugger (so we're dealing with a relatively huge number of properties).
Comment 6•12 years ago
|
||
I've seen something similar to comment 5 with console.dir on Linux. The embedded iframe appears blank initially, or in other cases it becomes empty after a click or a scroll event. I think it always reappears after a few seconds though (or maybe after a few more clicks/scrolls).
Comment 7•12 years ago
|
||
Maybe roc knows someone who can look into this.
Comment 8•12 years ago
|
||
crash is in view manager. Probably not a debugger bug. Moving to XUL.
Also, according to the graph, this bug peaked around the 5th of December and then dropped off. Wagering this was fixed but leaving it up to the component overseers to make a call.
Component: Developer Tools: Debugger → XUL
Product: Firefox → Core
Comment 9•12 years ago
|
||
There are some super serious rendering artifacts going on on a stock ubuntu and latest nightly.
STR:
1. Go to http://htmlpad.org/debugger/
2. Open debugger
3. (optional) Click on the cog wheel on the right and select "Show variables filter box" - this makes the artifacts 10x crazier
4. Click on the 'Click me' button in the page
5. Hover 'window'
See attached video. This is trippy!
Comment 10•12 years ago
|
||
This happens in the wild as well, on Windows. See bug 956758.
I can reproduce the bug in comment #9. No idea whether it's related to the crash.
Mats, can you look into comment #9?
Assignee: nobody → matspal
Comment 13•12 years ago
|
||
The STR in comment 9 works for me in Nightly 29.0a1 (2014-02-01) Linux64 and OSX.
WFM also in Aurora 28.0a2 (2014-02-01) on OSX.
Assignee: matspal → nobody
Comment 16•11 years ago
|
||
Same here on Ubuntu 13.10. I wonder if it's the Nvidia+Intel i5's processor both running that could be part of the problem? I haven't done anything to disable the Nvidia or set GPU switching.
Comment 17•11 years ago
|
||
Can anyone still reproduce the crash or see rendering artifacts in the latest Nightly?
We did some nsViewManager changes recently that might have fixed the crash.
Flags: needinfo?(jgriffiths)
Comment 19•11 years ago
|
||
Thanks for testing.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•