Bug 91848 - [IVB] Segfault in intel_mipmap_tree.c:2571 calling glReadPixels from mpv on wayland
Summary: [IVB] Segfault in intel_mipmap_tree.c:2571 calling glReadPixels from mpv on w...
Status: RESOLVED FIXED
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/DRI/i965 (show other bugs)
Version: git
Hardware: Other Linux (All)
: medium normal
Assignee: Intel 3D Bugs Mailing List
QA Contact: Intel 3D Bugs Mailing List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-09-02 09:32 UTC by Kevin Mitchell
Modified: 2016-12-10 13:50 UTC (History)
3 users (show)

See Also:
i915 platform:
i915 features:

Attachments
gdb -ex run --no-config --force-window --idle --msg-level=all=trace build/mpv (59.79 KB, text/plain)
2015-09-02 09:32 UTC, Kevin Mitchell 		Details
View All

Description Kevin Mitchell 2015-09-02 09:32:46 UTC 
Created attachment 118048 [details]
gdb -ex run --no-config --force-window --idle --msg-level=all=trace build/mpv

When taking a "window" screenshot in mpv (Ctrl+S), which reads the image directly from the framebuffer using glReadPixels on wayland, I get the attached backtrace which terminates at

intel_miptree_attach_map (mode=1, h=1, w=960, y=0, x=0, slice=0, level=0, mt=0x0) at ../../../../../../../src/mesa/drivers/dri/i965/intel_mipmap_tree.c:2571

This works fine on X11.

Chipset: moble IvyBridge
mesa:4de86e1371b0d59a5b9a787b726be3d373024647
mpv: a8e6de90fee1699c5de89eb1ae2182ceb096a65b
linux: 4.1.4
Comment 1 Matt Turner 2015-09-02 18:57:22 UTC 
Anuj sent some patches that I suspect will fix this. I wasn't sure how to confirm their correctness. I'll find them and link them here for you to test.
Comment 2 Matt Turner 2016-11-03 22:18:01 UTC 
Please test a new version of Mesa (12 or 13) and mark as REOPENED
if you can reproduce and RESOLVED/* if you cannot reproduce.
Comment 3 Kevin Mitchell 2016-12-10 13:50:04 UTC 
Sorry for the delay. I don't usually use wayland. I tested with 
libegl1-mesa=13.0.2-1 on Debian and it now works. Thanks.

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.