Summary: | crash in intel_miptree_create_for_dri_image due to invalid bo | ||
---|---|---|---|
Product: | Mesa | Reporter: | ubitux <freedesktop> |
Component: | Drivers/DRI/i965 | Assignee: | Intel 3D Bugs Mailing List <intel-3d-bugs> |
Status: | RESOLVED DUPLICATE | QA Contact: | Intel 3D Bugs Mailing List <intel-3d-bugs> |
Severity: | normal | ||
Priority: | medium | CC: | evangelos |
Version: | 17.3 | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
ubitux
2018-01-11 07:22:21 UTC
Since the trace was randomly changing, I added some debug in intel_update_image_buffer(), and it looks like there is a memory corruption happening in __DRIimageRec struct (intel one): buffer=0x55fdda4e3f00 buffer->screen=0x55fdda4c2130 buffer->bo=0x1 buffer->pitch=0xda196040 buffer->internal_format=0x55fd buffer->dri_format=0x00000004 bo is definitely a broken pointer, 0xda196040 is way too huge to be a valid pitch (even interpreted as negative), 0x55fd doesn't look like a valid GL internal format (previous calls are 0x1907 / GL_RGB), dri_format also got changed from 0x1002. I didn't check any further in the struct to see where the corruption starts, maybe I should? Most likely the same issue as in bug 104214. Try the patch from comment 29 on that bug. I can confirm the patch in bug 104214 fixes this issue as well. Thank you. *** This bug has been marked as a duplicate of bug 104214 *** |
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.