XCB crash while Video Rendering in multithreded application Post: 302932390

Sponsored Content

Operating Systems Linux Red Hat XCB crash while Video Rendering in multithreded application Post 302932390 by anuachin on Wednesday 21st of January 2015 09:57:06 AM

01-21-2015

Registered User

XCB crash while Video Rendering in multithreded application

I encounter the following crash on RHEL 7.0 when I run a multithreaded video rendering application using GLFW and OpenGL. OpenGL version is 2.1 and MESA version is 9.3.0

Following is the back trace of the multi-threaded program I am working on:
**************************************************************************************************** *******************

Code:

#0  0x00007f0970e75bb9 in __GI_raise (sig=sig entry=6)
    at ../nptl/sysdeps/unix/sysv/linux/raise.c:56
#1  0x00007f0970e78fc8 in __GI_abort () at abort.c:89
#2  0x00007f0970e6ea76 in __assert_fail_base (
    fmt=0x7f0970fc0370 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", 
    assertion=assertion entry=0x7f096f7c9615 "!c->out.queue_len", 
    file=file entry=0x7f096f7c9600 "../../src/xcb_conn.c", 
    line=line entry=186, function=function entry=0x7f096f7c9630 "write_vec")
    at assert.c:92
#3  0x00007f0970e6eb22 in __GI___assert_fail (
    assertion=0x7f096f7c9615 "!c->out.queue_len", 
    file=0x7f096f7c9600 "../../src/xcb_conn.c", line=186, 
    function=0x7f096f7c9630 "write_vec") at assert.c:101
#4  0x00007f096f7bde5b in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#5  0x00007f096f7be191 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#6  0x00007f096f7be8a7 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#7  0x00007f096f7be9c8 in xcb_take_socket ()
   from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#8  0x00007f0971d84a38 in ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
#9  0x00007f0971d85259 in _XFlush () from /usr/lib/x86_64-linux-gnu/libX11.so.6
#10 0x00007f0971d87c75 in _XGetRequest ()
   from /usr/lib/x86_64-linux-gnu/libX11.so.6
#11 0x00007f0971d810bb in XSync () from /usr/lib/x86_64-linux-gnu/libX11.so.6
---Type <return> to continue, or q <return> to quit---
#12 0x00007f09720c075a in ?? () from /usr/lib/x86_64-linux-gnu/mesa/libGL.so.1
#13 0x000000000040dc89 in _glfwPlatformSwapBuffers ()
#14 0x0000000000404e00 in glfwSwapBuffers ()
#15 0x0000000000403e4f in thread_main (data=0x7fff243ec830) at threads.c:67
#16 0x000000000040f747 in _thrd_wrapper_function (aArg=0x2242f30)
    at tinycthread.c:346
#17 0x00007f097120d182 in start_thread (arg=0x7f096b01d700)
    at pthread_create.c:312
#18 0x00007f0970f39fbd in clone ()
    at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Please suggest the resolution.

Last edited by Don Cragun; 01-21-2015 at 05:40 PM.. Reason: Add CODE tags.

anuachin

View Public Profile for anuachin

Find all posts by anuachin

7 More Discussions You Might Find Interesting

1. UNIX Desktop Questions & Answers

Unix GUI rendering

Does anyone know why Fonts and most Graphics in KDE and Gnome are rendered rather badly. There are some text editors in KDE where the font is just horrible as far as legible. Any links or knowledge on this topic would be grealy appreciated. A Huge Unix/Linux Fan Gregg

2. UNIX for Advanced & Expert Users

Exceed and offscreen rendering

Hi everyone. I made a program which renders a 3D scene into a pbuffer/pixmap (if pbuffer aren't supported) in order to export it to a postscript file. On a RHEL4 (32/64 bits) or whatever distribution may be, it works just fine. I'm using Exceed when I'm working under WinXP and each time I run my...

3. Programming

socket system call can not succedd right after application crash.

hello all, I have developed a server application in C for ulinux kernel 2.6.It works very fine; creating a socket, binding it to a port, listening for incoming sockets and accepting them ,all finish without any error. But there is a problem regarding application crash.After an intentionally...

4. Programming

Client/Server Socket Application - Preventing Client from quitting on server crash

Problem - Linux Client/Server Socket Application: Preventing Client from quitting on server crash Hi, I am writing a Linux socket Server and Client using TCP protocol on Ubuntu 9.04 x64. I am having problem trying to implement a scenario where the client should keep running even when the...

5. Programming

How install XCB?

In my mint I can't found <xcb/xcb.h> while in Ubuntu it was. ---------- Post updated at 03:11 PM ---------- Previous update was at 01:43 PM ---------- Is possibility install XCB from sources: from linuxfromscratch.org steps: x7proto.html xcb-proto.html libXau.html libxcb.html

6. HP-UX

Sudden application crash in servers

Hi, This weekend there was a sudden application crash in the server. I did not know where to start to investigate the problem, so I first looked into the /var/adm/syslog/syslog.log, and this was what I found : Dec 17 00:38:02 L28bi01 sshd: error: accept: No buffer space available Dec 17...

7. Fedora

Fedora 30 and Slackware 14.2, how to obtain the same rendering?

Look this very good rendering on Slackware 14.2 in my opinion is near perfect. https://i.stack.imgur.com/q5trL.png Now look the same page on Fedora 30 https://i.stack.imgur.com/FBQv7.png In my opinion the fonts on Fedora are too small and difficult to read, I prefer the fat fonts of...

LEARN ABOUT HPUX

cr_open

cr_open(3)						     Library Functions Manual							cr_open(3)

NAME

       cr_open() - open crash dump for reading

SYNOPSIS

DESCRIPTION

       The library call opens a crash dump and passes back a crash dump descriptor.

       The path argument points to a path name naming a crash dump directory or file, and must not exceed bytes in length.

       The CRASH * to which crash_cb points is set to a crash dump descriptor, which can then be passed to the other functions to access the crash
       dump.

       flags is a bitmask of zero or more of the following flag values, which affect the operation of future calls to libcrash routines  for  this
       crash dump, except for cr_verify(3), which has its own flags parameter.

       The library will not attempt to verify checksums of files in the crash
			     dump if this flag is set.

       The library will write messages to stderr during time-consuming operations
			     (decompressions and checksums) if this flag is set.

RETURN VALUE

       Returns zero for success.  Other possible return values are described in libcrash(5).

EXAMPLES

       The following call to opens crash dump contained in the directory and returns the crash dump descriptor For an example of reading the crash
       dump see the cr_read(3) manual entry.

AUTHOR

       was developed by HP.

SEE ALSO

       cr_close(3), cr_perror(3), libcrash(5).

																	cr_open(3)