Closed
Bug 737279
Opened 13 years ago
Closed 9 years ago
Crash in mozilla::gfx::DrawTargetD2D::FillGlyphs
Categories
(Core :: Graphics: Canvas2D, defect)
Tracking
()
RESOLVED
WORKSFORME
Tracking | Status | |
---|---|---|
firefox12 | - | affected |
firefox13 | --- | unaffected |
firefox14 | --- | unaffected |
People
(Reporter: epinal99-bugzilla2, Unassigned)
Details
(Keywords: crash, regression, reproducible)
Crash Data
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0) Gecko/20120319 Firefox/13.0a2
Build ID: 20120319042013
Steps to reproduce:
From https://bugzilla.mozilla.org/show_bug.cgi?id=668344#c38
Crash occurs only in FF13 (afaik).
STR:
1) Open http://people.mozilla.org/~jdaggett/tests/subpixelexplorer.html
2) Disable hardware acceleration
3) Back to tab and click on button 'redraw'
CR: https://crash-stats.mozilla.com/report/index/bp-43f0f215-321a-4fb6-9755-034bf2120320
Signature mozilla::gfx::DrawTargetD2D::FillGlyphs(mozilla::gfx::ScaledFont*, mozilla::gfx::GlyphBuffer const&, mozilla::gfx::Pattern const&, mozilla::gfx::DrawOptions const&)
Crashing Thread
Frame Module Signature [Expand] Source
0 xul.dll mozilla::gfx::DrawTargetD2D::FillGlyphs gfx/2d/DrawTargetD2D.cpp:885
1 xul.dll nsCanvasBidiProcessorAzure::DrawText content/canvas/src/nsCanvasRenderingContext2DAzure.cpp:3089
2 xul.dll nsBidiPresUtils::ProcessText layout/base/nsBidiPresUtils.cpp:1824
3 xul.dll nsCanvasRenderingContext2DAzure::DrawOrMeasureText content/canvas/src/nsCanvasRenderingContext2DAzure.cpp:3335
Crash Signature: [@ mozilla::gfx::DrawTargetD2D::FillGlyphs(mozilla::gfx::ScaledFont*, mozilla::gfx::GlyphBuffer const&, mozilla::gfx::Pattern const&, mozilla::gfx::DrawOptions const&) ]
Summary: Firefox 13: crash in mozilla::gfx::DrawTargetD2D::FillGlyphs → Crash in mozilla::gfx::DrawTargetD2D::FillGlyphs
Keywords: reproducible
Comment 1•13 years ago
|
||
(In reply to Loic from comment #0)
> User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0) Gecko/20120319
> Firefox/13.0a2
> https://crash-stats.mozilla.com/report/index/bp-43f0f215-321a-4fb6-9755-
> 034bf2120320
The crash ID is related to 12.0a2/20120313042010. Does it happen on 13.0a2?
Severity: normal → critical
QA Contact: untriaged → canvas.2d
(In reply to Scoobidiver from comment #1)
> The crash ID is related to 12.0a2/20120313042010. Does it happen on 13.0a2?
Aurora was FF12 when I reproduced the crash then updated to FF13 after the restart, that's why I got confused.
But the affected version is FF12 (now in beta).
New CR: https://crash-stats.mozilla.com/report/index/bp-bfd47d12-ac9f-41ff-bc96-498632120320
Comment 3•13 years ago
|
||
I can reproduce in 12.0b1, I can't in 11.0, 13.0a2, 14.0a1.
Disabling HW acceleration is not a common task (only one crash in 12.0b1).
Status: UNCONFIRMED → NEW
status-firefox12:
--- → affected
status-firefox13:
--- → unaffected
status-firefox14:
--- → unaffected
Ever confirmed: true
Keywords: regression
Comment 4•13 years ago
|
||
(In reply to Scoobidiver from comment #3)
> I can reproduce in 12.0b1, I can't in 11.0, 13.0a2, 14.0a1.
>
> Disabling HW acceleration is not a common task (only one crash in 12.0b1).
Does this reproduce if hardware acceleration is disabled from the beginning? We do blocklist drivers from using D2D, so this could be a bigger problem when pushed to our general audience.
tracking-firefox12:
--- → ?
Comment 5•13 years ago
|
||
(In reply to Alex Keybl [:akeybl] from comment #4)
> Does this reproduce if hardware acceleration is disabled from the beginning?
No. In addition, it's recommended to restart Firefox after modifying this option although it isn't written in the UI (see bug 593027).
No, and the page http://people.mozilla.org/~jdaggett/tests/subpixelexplorer.html needs to be open before disabling HWA.
status-firefox12:
affected → ---
status-firefox13:
unaffected → ---
status-firefox14:
unaffected → ---
tracking-firefox12:
? → ---
Oops, something goes wrong with the flags. Can you remove the modifications please?
Updated•13 years ago
|
status-firefox12:
--- → affected
status-firefox13:
--- → unaffected
status-firefox14:
--- → unaffected
tracking-firefox12:
--- → ?
Comment 8•13 years ago
|
||
(In reply to Scoobidiver from comment #5)
> No. In addition, it's recommended to restart Firefox after modifying this
> option although it isn't written in the UI (see bug 593027).
Thanks for the explanation. Given that, no need to track for 12.
Another testcase about this crash:
1. Be sure HWA is enabled
2. Open this JS demo http://js1k.com/2012-love/demo/1243
3. Disable HWA
Result: FF12 crashes immediately.
CR: https://crash-stats.mozilla.com/report/index/bp-0aeb028f-98ed-48aa-88f1-799472120408
Updated•9 years ago
|
Crash Signature: [@ mozilla::gfx::DrawTargetD2D::FillGlyphs(mozilla::gfx::ScaledFont*, mozilla::gfx::GlyphBuffer const&, mozilla::gfx::Pattern const&, mozilla::gfx::DrawOptions const&) ] → [@ mozilla::gfx::DrawTargetD2D::FillGlyphs(mozilla::gfx::ScaledFont*, mozilla::gfx::GlyphBuffer const&, mozilla::gfx::Pattern const&, mozilla::gfx::DrawOptions const&) ]
[@ mozilla::gfx::DrawTargetD2D::FillGlyphs ]
Comment 10•9 years ago
|
||
I'd tried this issues on MAC OS, Ubuntu and Windows platform and I can't find it any more. I will close this bug. Reopen if anyone still can reproduce it. Thanks.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•