573013 - Mozilla crashes the display driver when D2D is enabled [@ _fill_rectangles]

Status: RESOLVED FIXED

(Core :: Graphics, defect)

Description

[José Jeria]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.3a6pre) Gecko/20100617 Minefield/3.7a6pre
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.3a6pre) Gecko/20100617 Minefield/3.7a6pre

I get these crashes quite often, but no crash report is usually generated.

What happens is that Firefox stops responding and then eventually crashes. Windows 7 reports that the display driver was restarted due to a crash.

Reproducible: Always

Steps to Reproduce:
Happens randomly. On any webpage.



Crash report: bp-ac52217c-a42b-4afa-8c67-1b2a22100618

Comment 1

[timeless]

If your display driver is crashing, that's a bug in the display driver, send a report to your display driver vendor.

It's a very simple contract: display drivers must accept all input (including bad input) and not crash. Just as web browsers must accept all input (including bad web pages) and not crash.

Signature	_fill_rectangles
UUID	ac52217c-a42b-4afa-8c67-1b2a22100618
Time 	2010-06-18 05:19:31.329298
Uptime	5944
Last Crash	2255258 seconds (3.7 weeks) before submission
Install Age	9538 seconds (2.6 hours) since version was first installed.
Product	Firefox
Version	3.7a6pre
Build ID	20100617161137
Branch	1.9.2
OS	Windows NT
OS Version	6.1.7600
CPU	x86
CPU Info	GenuineIntel family 6 model 23 stepping 6
Crash Reason	EXCEPTION_STACK_OVERFLOW
Crash Address	0x635d215b
Email Address	

User Comments	
Processor Notes 	
EMCheckCompatibility	False
Crashing Thread
Frame 	Module 	Signature [Expand] 	Source
0 	xul.dll 	_fill_rectangles 	gfx/cairo/cairo/src/cairo-surface-fallback.c:643
1 	xul.dll 	_clip_and_composite_trapezoids 	gfx/cairo/cairo/src/cairo-surface-fallback.c:785
2 	xul.dll 	_cairo_surface_fallback_paint 	gfx/cairo/cairo/src/cairo-surface-fallback.c:1044
3 	xul.dll 	_cairo_surface_paint 	gfx/cairo/cairo/src/cairo-surface.c:2020
4 	xul.dll 	_cairo_surface_fallback_clone_similar 	gfx/cairo/cairo/src/cairo-surface-fallback.c:1830
5 	d3d10_1core.dll 	d3d10_1core.dll@0x150f 	

Your crash report included a url which doesn't seem very interesting, would you mind if i indicated the domain in this report?

Comment 2

[José Jeria]

(In reply to comment #1)
> Your crash report included a url which doesn't seem very interesting, would you
> mind if i indicated the domain in this report?

No, that's fine, go ahead

Comment 3

[timeless]

thanks.

the site was coveritlive.com (the url itself had more information, but didn't seem to yield something useful).

Comment 4

[José Jeria]

I have now updated the graphic driver and I am not seeing this crash/hang anymore. Should this bug be closed?

Comment 5

[Oskar Ivanić (:icecold)]

Got a crash with 258.69 drivers. 
http://crash-stats.mozilla.com/report/index/bp-318857bd-caae-4e70-bc4b-25dbc2100704

Comment 6

[Kevin Brosnan]

Just crashed - Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.0b5pre) Gecko/20100824 Minefield/4.0b5pre

mozilla.widget.render-mode;-1
gfx.font_rendering.directwrite.enabled

Comment 7

[José Jeria]

Note that this also crashed the IE preview as well. Both Firefox and IE stopped crashing when I updated the drivers.

Comment 8

[Vladimir Vukicevic [:vlad] [:vladv] (needinfo me, slow to respond)]

Sounds like driver blacklist time.

Comment 9

[Bas Schouten (:bas.schouten)]

(In reply to comment #8)
> Sounds like driver blacklist time.

We should be able to properly recover from these particular problems, we're working on fixing that, I think that's probably a better idea for these kind of issues.

Comment 10

[Bas Schouten (:bas.schouten)]

Attachment: Report better errors from acquire_source/dest

Comment 11

[Kevin Brosnan]

I have nVidia's 258.96 drivers installed.

Comment 12

[Jeff Muizelaar [:jrmuizel]]

Comment on attachment 469053 [details] [diff] [review]
Report better errors from acquire_source/dest

Seems better

Comment 13

[Bas Schouten (:bas.schouten)]

http://hg.mozilla.org/mozilla-central/rev/cf9da3a00368

The rest of this issue will be delt with in driver reset bugs.