Open
Bug 1141073
Opened 10 years ago
Updated 2 years ago
Partial device lost causes presentation to stop working
Categories
(Core :: Graphics: Layers, defect)
Tracking
()
NEW
People
(Reporter: jrmuizel, Assigned: jrmuizel)
Details
(Whiteboard: [gfx-noted])
Here's a demonstration of the problem:
https://mega.co.nz/#!CYIlnb6b!7VsC5OxxqtZ5ad31F9HXR-s-LyMoI-dqt5I6jLKvgcw
Updated•10 years ago
|
OS: Mac OS X → Windows 8
Whiteboard: [gfx-noted]
Assignee | ||
Comment 1•10 years ago
|
||
marco_pal, it should be possible to get a regression window on the inbound builds. That should give us a narrower range to work with. Can you get one?
Flags: needinfo?(marco_pal)
Assignee | ||
Updated•10 years ago
|
Assignee: nobody → jmuizelaar
I don't know if that's how you do it, but I used the mozregression tool setting it from release 32 to 36. I've tried every nightly but in the end everyone worked correctly. I don't know why it's different with the build you provided in bug 1067470
Flags: needinfo?(marco_pal)
Assignee | ||
Comment 3•10 years ago
|
||
Do the windows that stop painting every start painting again normally when this problem happens?
Assignee | ||
Comment 4•10 years ago
|
||
Also, can you reproduce this problem with FF37?
Recap
Firefox 36.0 release NO PROBLEM
Firefox 37.0 beta 6 NO PROBLEM
https://hg.mozilla.org/try/rev/3f977c607fc1 stalls on addons "activate" menu and on awesome bar input, then freeze that window and prints error 887a0005 on every supposed update on that window. Like in the video I posted. If I switch to a tab with flash it will draw correctly above the freezed tab. It never recovers from freezing. If minimized and reopened it goes blank. After a while or maximized might crash:
https://crash-stats.mozilla.com/report/index/627b820a-e294-420c-ac15-68f532150320
https://crash-stats.mozilla.com/report/index/1f0bd29a-b195-4462-b908-cf8b82150320
https://hg.mozilla.org/try/rev/0270fbc337a9 in the same conditions it crash, without freezing or printing anything on console. See:
https://crash-stats.mozilla.com/report/index/8520a3d3-f006-4c67-9962-0ad092150319
https://crash-stats.mozilla.com/report/index/667a281f-3e38-43fb-b15b-22ad42150319
https://hg.mozilla.org/try/rev/84df7b5a88d6 identical to the previous except the crash signature turns back to the first one
https://crash-stats.mozilla.com/report/index/ca42b2d6-a677-4586-9b62-473a32150320
https://crash-stats.mozilla.com/report/index/2a761587-14e0-4c4b-9e96-a5bba2150320
I will try the last one when it will finish building
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•