Bug 29430 - [UXA] Crash due assert (uxa_pixmap_is_offscreen(src_pixmap));
Summary: [UXA] Crash due assert (uxa_pixmap_is_offscreen(src_pixmap));
Status: RESOLVED FIXED
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/intel (show other bugs)
Version: git
Hardware: x86-64 (AMD64) Linux (All)
: medium major
Assignee: Chris Wilson
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-08-06 19:02 UTC by Cyril Brulebois
Modified: 2010-08-25 07:02 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
bt full (3.97 KB, text/plain)
2010-08-06 19:03 UTC, Cyril Brulebois
no flags Details

Description Cyril Brulebois 2010-08-06 19:02:33 UTC
Chip: 00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07)
Kernel: 2.6.32 as patched by Debian (many DRM fixes from 2.6.33.y, etc.)
Server: 1.7.7 as patched by Debian

With either 2.12.0+legacy branch or master (as of 6304cb0) I'm hitting the following assert:
./uxa/uxa-glyphs.c:986
                                assert (uxa_pixmap_is_offscreen(src_pixmap));

To reproduce, just start the 'sm' program (http://www.joachim-breitner.de/projects#screen-message) with a random string, and exit it (hitting 'q').
Comment 1 Cyril Brulebois 2010-08-06 19:03:30 UTC
Created attachment 37655 [details]
bt full
Comment 2 Chris Wilson 2010-08-25 07:02:34 UTC
commit 68a5ad497b557ab9e8bff301098ea78c84d385a2
Author: Chris Wilson <chris@chris-wilson.co.uk>
Date:   Wed Aug 25 14:59:04 2010 +0100

    uxa: Fallback if faced with large A1 glyphs.
    
    Rather than assert, we should fixup the use of large A1 glyphs. However,
    the simplest approach is to simply fallback to s/w.
    
    Fixes:
    
      Bug 29430 - [UXA] Crash due assert (uxa_pixmap_is_offscreen(src_pixmap));
      https://bugs.freedesktop.org/show_bug.cgi?id=29430
    
    Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>


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.