Bug 69867 - [Bisected] cairo-trace crash
Summary: [Bisected] cairo-trace crash
Status: CLOSED NOTABUG
Alias: None
Product: cairo
Classification: Unclassified
Component: xlib backend (show other bugs)
Version: unspecified
Hardware: All Linux (All)
: medium major
Assignee: Chris Wilson
QA Contact: cairo-bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-09-27 01:54 UTC by meng
Modified: 2013-10-17 07:24 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Attachments

Description meng 2013-09-27 01:54:11 UTC 
System Environment:       
----------------------------------------------
Platform:  IVB/HSW
Libdrm:	(master)libdrm-2.4.46-42-gbf4a7cd4b2456d4dc93a86bbcc51eba4ae73390a
Mesa:	(master)fe2528c0b69d5719b15d926ada9424cac7569b9c
Cairo:	(master)337ab1f8d9e29086bfb4001508b28835b41c6390
Libva:	(staging)f5c913765e6af38d835cacf339054ccc60bddefb
Libva_intel_driver: (staging)f6685c309d94fb7679c9772703c8790cb71cdd73
Kernel:	(drm-intel-nightly) 24c8329416b54b79655afe45370cf3d46f41e283

Bug detailed description:
----------------------------------------------
cairo-trace crash on IVB/HSW, the output:
[  0]     xlib                 firefox-tron Error during replay, line 27: invalid value (typically too big) for the size of the input (surface, pattern, etc.)

It’s cairo regression, bisecting show that the first bad commit is:
commit 0266cb821fbf0bdd307af7bbcbbd22c4a14201fc
Author: Chris Wilson <chris@chris-wilson.co.uk>
Date:   Thu Sep 5 16:13:56 2013 +0100

    script: Add support for replaying device-scale

    Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>

Reproduce steps:
---------------------------------------------
1, xinit&
2, vblank_mode=0 CAIRO_TEST_TARGET=xlib  /home/cairo/perf/cairo-perf-trace firefox-tron.trace
Comment 1 Chris Wilson 2013-09-27 08:08:29 UTC 
The binary cairo-trace files are intentionally unstable across API changes. Recreate the binary traces from the compressed originals.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.