On Tue, Jan 31, 2017 at 12:07:48AM -0800, Philip Guenther wrote: > Sun, 29 Jan 2017, Philip Guenther wrote: > ... > > semarie@, you can consistently trigger that kernel log message, perhaps > you can try reproducing it with this patch and see if it goes away?
it is a bit better now: I have only one error message instead of two. from the two firefox processes: - 90712 parent - 97188 contentproc (child) (firefox:90712): Gdk-ERROR **: The program 'firefox' received an X Window System error. This probably reflects a bug in the program. The error was 'RenderBadPicture (invalid Picture parameter)'. (Details: serial 3130 error_code 143 request_code 139 (RENDER) minor_code 7) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the GDK_SYNCHRONIZE environment variable to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) [Child 97188] ###!!! ABORT: Aborting on channel error.: file /usr/obj/ports/firefox-51.0/firefox-51.0/ipc/glue/MessageChannel.cpp, line 2056 [Child 97188] ###!!! ABORT: Aborting on channel error.: file /usr/obj/ports/firefox-51.0/firefox-51.0/ipc/glue/MessageChannel.cpp, line 2056 Trace/BPT trap dmesg has: coredump of firefox(90712), write failed: errno 14 before, I had two lines (one for each processes). I use this script for reproduce: https://p.iotek.org/d74 (but landry@ told me he didn't reproduce the Gdk-ERROR, so some elements in my environment should be missing). thanks. -- Sebastien Marie
