Bug 100075 - st/va raises segmentation fault while using videotestsrc with gstreamer
Summary: st/va raises segmentation fault while using videotestsrc with gstreamer
Status: NEW
Alias: None
Product: Mesa
Classification: Unclassified
Component: Other (show other bugs)
Version: git
Hardware: Other All
: medium normal
Assignee: mesa-dev
QA Contact: mesa-dev
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-03-06 06:55 UTC by gurkirpal204
Modified: 2017-03-20 08:24 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
gdb backtrace log (17.76 KB, text/plain)
2017-03-06 06:55 UTC, gurkirpal204
Details
backtrace (4.83 KB, text/plain)
2017-03-19 23:28 UTC, gurkirpal204
Details

Note You need to log in before you can comment on or make changes to this bug.
Description gurkirpal204 2017-03-06 06:55:39 UTC
Created attachment 130082 [details]
gdb backtrace log

gst-launch-1.0 videotestsrc \! video/x-raw, format=RGBx \! vaapisink
Running the pipeline causes causes a blank window to open and segmentation fault occurs.
Comment 1 Julien Isorce 2017-03-16 12:42:52 UTC
Thx Gurkirpal for the report.

The other day I was going further into https://bugzilla.gnome.org/show_bug.cgi?id=779642 and I wonder if it is not the same issue in the end, see its commet #6.
Comment 2 gurkirpal204 2017-03-19 23:28:24 UTC
Created attachment 130320 [details]
backtrace

changed backtrace log to the right one.
Comment 3 Julien Isorce 2017-03-20 08:24:34 UTC
Thx Gurkirpal, this time the backtrace looks different than the gst bug I pointed above.

I get the same result with AMD, dri/radeonsi_drv_video.so . Note it crashes with RGBx and BGRx but not with RGBA and BGRA.

(gdb) info locals
res = <optimized out>
desc = <optimized out>
nr_components = <optimized out>
buf = 0x7fffd8070320
sv_templ = {reference = {count = 6291460}, target = PIPE_BUFFER, format = 4041780302, texture = 0x6dfd50, context = 0x7fffd8000020, u = {
    tex = {first_layer = 192, last_layer = 0, first_level = 0, last_level = 0}, buf = {offset = 192, size = 0}}, swizzle_r = 0, 
  swizzle_g = 4, swizzle_b = 4, swizzle_a = 1}
pipe = 0x86ed00
i = 0
j = <optimized out>
component = 0
__PRETTY_FUNCTION__ = "vl_video_buffer_sampler_view_components"

I can read buf size 0 but it would require further investigations.


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.