| Summary: | X core dump related ot intel driver | ||||||
|---|---|---|---|---|---|---|---|
| Product: | xorg | Reporter: | Toralf Förster <toralf.foerster> | ||||
| Component: | Driver/intel | Assignee: | Chris Wilson <chris> | ||||
| Status: | RESOLVED FIXED | QA Contact: | Xorg Project Team <xorg-team> | ||||
| Severity: | normal | ||||||
| Priority: | medium | ||||||
| Version: | 7.6 (2010.12) | ||||||
| Hardware: | Other | ||||||
| OS: | All | ||||||
| URL: | http://bugs.winehq.org/show_bug.cgi?id=28198 | ||||||
| Whiteboard: | |||||||
| i915 platform: | i915 features: | ||||||
| Attachments: |
|
||||||
|
Description
Toralf Förster
2011-08-28 14:06:05 UTC
commit 0a74cd77a3f462d5d2707bf1f35663279bcb9be5 Author: Chris Wilson <chris@chris-wilson.co.uk> Date: Mon Aug 29 10:41:26 2011 +0100 video: check that the pixmap exists before use Now, the pixmap being used is meant to the Screen pixmap and by rights that has to exists in a GPU buffer! Evidence contrary to the above exists and so we had better check that we have a bo before using... Reported-by: Toralf Förster <toralf.foerster@gmx.de> Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=40439 Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk> That should stop the crash (I believe), I just don't understand how that was possible in the first place... Created attachment 50654 [details]
valgrind output for mesa classic (sw and i965 module)
I re-run with intel 2.16.0-15-g0ac4b97 the given wine test case, the valgrind output is attached here.
So far no crash observed nor occurred (monitor configuration is different from the original report however, currently I've a dual-head (LVDS+VGA) , whereas the bug occured w/ an external attached DVI monitor).
:-)
*** Bug 40440 has been marked as a duplicate of this bug. *** Just for the record : Thx Chris, that patch solves few more crashes under wine too (eg. :within d3d8 and d3d9 directory) - now those test cases do only fail instead crash ;) |
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.