[Bug 755675] gtkglsink: UI freezes when the window has a GtkHeaderBar and runs on top of X11

[GStreamer (GNOME Bugzilla)]

https://bugzilla.gnome.org/show_bug.cgi?id=755675

--- Comment #7 from Matthew Waters <ystreet00 at gmail.com> ---
(In reply to Ian from comment #6)
> (In reply to Matthew Waters from comment #5)
> > In the gtk source directory there are some examples for their GL stuff.
> 
> I couldn't find this directory you're talking about, and couldn't find any
> Python example on the internet, sorry. The example in gtk3-demo works fine,
> though, but I wasn't able to compile it from the provided source because I
> don't know how to C. :/

Ok, so for example for for gdkgears, edit
https://git.gnome.org/browse/gtk+/tree/tests/gdkgears.c#n117 to add the header
bar.  Them execute "make" to build, then attempt to run the gdkgears program
and see if the problem exists there.  You can attempt to do the same to the
gtk3-demo example.  The steps are the same.  Edit
https://git.gnome.org/browse/gtk+/tree/demos/gtk-demo/glarea.c#n374. make. Then
attempt to run the gtk3-demo GL example.

> > 1. Does running with LIBGL_ALWAYS_SOFTWARE=1 make it work?
> 
> No, but it now displays the 1st frame, instead of a black screen.

That's weird.  It works fine here.  What are your Mesa, X11, libdrm, kernel,
etc versions?

> > 2. Providing an apitrace trace of the execution on your AMD card.  See
> > https://github.com/apitrace/apitrace/blob/master/docs/USAGE.markdown for
> > usage details.  apitrace trace python3 file.py should work fine.
> > 3. Attempt to re-run the trace and see if the correct output is displayed.
> 
> Well, the output was the same every time I ran it. I'll add the log as an
> attachment. The *.trace files are big (70-80Mb each), could you tell me what
> would be the best way to send it to you?

Either a file sharing service somewhere or just the first 50 or so frames
should be sufficient to have a look and should fit under the 1600K attachment
limit on bugzilla with compression (gzip, lzma, etc)?

Running head -n<a number> file.trace > truncate.trace will truncate the trace
to <a number> function calls.  As a start, try <a number> = 5000.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.