366688 - Crash [@ fbBltOne] with testcase that uses ridge border, opacity and text-zoom

Status: RESOLVED WORKSFORME

(Core :: Graphics, defect)

Description

[Martijn Wargers (dead)]

Attachment: testcase

See testcase, which usually crashes for me within 5 seconds after opening.
You need to download the testcase to your computer, because of the use of code that needs enhanced privileges (text-zoom).

Talkback ID: TB28255461X
fbBltOne  [mozilla\gfx\cairo\libpixman\src\icbltone.c, line 290]
fbCompositeSolidMask_nx1xn  [mozilla\gfx\cairo\libpixman\src\fbpict.c, line 950]
_moz_cairo_pixman_composite  [mozilla\gfx\cairo\libpixman\src\fbpict.c, line 1892]
_cairo_image_surface_composite_trapezoids  [mozilla\gfx\cairo\cairo\src\cairo-image-surface.c, line 1026]
_cairo_surface_composite_trapezoids  [mozilla\gfx\cairo\cairo\src\cairo-surface.c, line 1465]
_cairo_surface_fallback_composite_trapezoids  [mozilla\gfx\cairo\cairo\src\cairo-surface-fallback.c, line 1159]
_cairo_surface_composite_trapezoids  [mozilla\gfx\cairo\cairo\src\cairo-surface.c, line 1475]
_composite_traps_draw_func  [mozilla\gfx\cairo\cairo\src\cairo-surface-fallback.c, line 498]
_clip_and_composite  [mozilla\gfx\cairo\cairo\src\cairo-surface-fallback.c, line 394]
_clip_and_composite_trapezoids  [mozilla\gfx\cairo\cairo\src\cairo-surface-fallback.c, line 638]
_cairo_surface_fallback_fill  [mozilla\gfx\cairo\cairo\src\cairo-surface-fallback.c, line 833]
_cairo_surface_fill  [mozilla\gfx\cairo\cairo\src\cairo-surface.c, line 1421]
_cairo_gstate_fill  [mozilla\gfx\cairo\cairo\src\cairo-gstate.c, line 1000]
_moz_cairo_fill_preserve  [mozilla\gfx\cairo\cairo\src\cairo.c, line 1961]
nsCSSRendering::DrawSide  [mozilla\layout\base\nscssrendering.cpp, line 568]
nsCSSRendering::PaintBorder  [mozilla\layout\base\nscssrendering.cpp, line 1865]

I suspect bug 340211 could be a similar issue.

Comment 1

[Martijn Wargers (dead)]

This is now worksforme with:
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a2pre) Gecko/20070131 Minefield/3.0a2pre
I guess this has been fixed somehow with the latest cairo update in Mozilla.