Closed
Bug 849038
Opened 11 years ago
Closed 6 years ago
crash while stressing pdf.js by scrolling in mozilla::layers::CanvasLayerD3D10::UpdateSurface
Categories
(Firefox :: PDF Viewer, defect, P3)
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: 6jju4k002, Unassigned)
References
Details
(Keywords: crash, Whiteboard: [pdfjs-c-performance])
Crash Data
This bug was filed from the Socorro interface and is report bp-6d18da0d-4ed1-4c61-92ef-64f882130307 . ============================================================= Build is: 20.0b3. Stressed the PDF.js system by opening the following tabs... http://www.lirmm.fr/~ducour/Publis/phtest.pdf opened in 2 tabs http://haskell.cs.yale.edu/wp-content/uploads/2011/02/rt-frp.pdf opened in 4x tabs. http://ompldr.org/vZjNrdw opened in one tab. Then did a lot of scrolling for a few minutes, switching occasionally between the pdf windows. The following memory metrics increased dramatically: canvas-2d-pixel-bytes gfx-d2d-surfacevram gfx-d2d-vram-drawtarget And just before the browser crashed.... gfx-d2d-vram-drawtarget was at approx 4MB gfx-d2d-surfacevram was reporting -ve memory!! Is probably related to the bug#842962 which shows high resource consumption, but no crash on scrolling. Is also related to crasher bug#834256 which with whose signature I saw with with similar operation is 20.0b2. See 834256#c19 for a similar of the memory increase pattern.
Forgot to mention: Repeatability: Always, but time taken to generate crash is unpredictable. Profile status: Almost new Mozilla profile. Only used for testing this bug, and bug#834256. additional hints to repeat: *Set pdf zoom to 200%, (as was done for the above crash) *Set pdf zoom to 400%, can even get crashing without scrolling, just by quickly switching between tabs. Generated the crash: bp-2f8d92bc-073f-4079-9b8d-e84d92130308 in this way.
Comment 2•11 years ago
|
||
CPU and memory usage is indeed high but Fx 20 Beta crashes only for me with the second method and it's an OOM: bp-4691e87e-c851-4d2f-bc10-909842130308.
Hardware: x86_64 → x86
And still present in beta 4 in same form: See crash: bp-5edd6354-8cde-4ef3-b01e-7b19a2130309 Prior to beta3, was getting mostly OOM bugs, with no stack trace. And occasionally the behaviour bug#834256
Comment 4•11 years ago
|
||
Was trying to reproduce bug 879320 to get an about:memory report but hit this crash instead. Nightly 24.
See Also: → 879320
Comment 5•10 years ago
|
||
FWIW, got this signature when trying https://bugzilla.mozilla.org/attachment.cgi?id=776628 (Bug 894231) with webgl.force-enabled;true webgl.prefer-native-gl;true bp-b6def0e7-b9c6-4316-9a2e-fb29a2140114
Comment 6•10 years ago
|
||
(In reply to XtC4UaLL [:xtc4uall] from comment #5) > FWIW, got this signature when trying > https://bugzilla.mozilla.org/attachment.cgi?id=776628 > (Bug 894231) with > > webgl.force-enabled;true > webgl.prefer-native-gl;true > > bp-b6def0e7-b9c6-4316-9a2e-fb29a2140114 This is a separate known issue from a few days ago.
Comment 7•10 years ago
|
||
Unable to reproduce on Fx29+
Updated•9 years ago
|
Crash Signature: [@ mozilla::layers::CanvasLayerD3D10::UpdateSurface()] → [@ mozilla::layers::CanvasLayerD3D10::UpdateSurface()]
[@ mozilla::layers::CanvasLayerD3D10::UpdateSurface]
Comment 8•6 years ago
|
||
Closing because no crash reported since 12 weeks.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•