Hello Guest

Sys.alert(...) causes giop_thread_request_push error console output

  • 0 Replies
  • 3957 Views
I ran into something weird. Sys.alert(...) causes the following messages to be printed to the console after you exit an application:
Code: [Select]
** (<unknown>:6180): CRITICAL **: giop_thread_request_push: assertion `tdata != NULL' failed

** (<unknown>:6180): CRITICAL **: giop_thread_request_push: assertion `tdata != NULL' failed

** (<unknown>:6180): CRITICAL **: giop_thread_request_push: assertion `tdata != NULL' failed

** (<unknown>:6180): CRITICAL **: giop_thread_request_push: assertion `tdata != NULL' failed

** (<unknown>:6180): CRITICAL **: giop_thread_request_push: assertion `tdata != NULL' failed

Test code:
Code: [Select]
import org.lwjgl.Sys;

public class SysAlertTest {

    public static void main(String[] args) throws InterruptedException {
        // Yay, no more Toolkit instantiation needed ;)
        Sys.alert("Title", "Message!");
    }
}

Happens on Linux (Ubuntu 9, 32 bit, Nvidia 8800). It does NOT happen on Windows XP (32 bit, ATI 1250x ). Happens with LWJGL 2.1.0 and latest 2.2.0 #246.

It's not a bug per se, because everything appears to work as expected and alert windows show up. Just when the app finally finishes, these four five messages get printed to the console, i.e. not when Sys.alert(...) is actually called but when Java exits. Multiple calls to Sys.alert(...) do not change the number of printed error messages.

Thought I'd mention this because it took some time to find out which call was responsible since the output is delayed until the app quits; in case somebody else runs into this.
« Last Edit: September 30, 2009, 07:59:47 by Ciardhubh »