URL:
  <http://savannah.gnu.org/bugs/?30892>

                 Summary: Deadlock on performSelectorOnMainThread:
                 Project: GNUstep
            Submitted by: jonathanosx
            Submitted on: Fri 27 Aug 2010 09:16:39 PM GMT
                Category: Backend
                Severity: 3 - Normal
              Item Group: Bug
                  Status: None
                 Privacy: Public
             Assigned to: None
             Open/Closed: Open
         Discussion Lock: Any

    _______________________________________________________

Details:

We are running into an occasional problem with our application on GNUstep
(Ubuntu 9.04) where we deadlock when attempting to call
performSelectorOnMainThread:  The back trace with the locked threads is
attached.  The only condition that I can see for this situation is that
somehow the outputFD of the pipe that is used to "trigger" the main run loop  
to pick-up is blocked and can't be written to (GSRunLoopThreadInfo of
NSThread.m).  I do notice that although NBLK_OPT is set for the inputFD, it
isn't set for outputFD which seems to be where the deadlock is occurring.

First, does anyone have an alternate (or clearer vision) of why this deadlock
condition is occuring?

Second, does anyone have a preferred solution other than to set the outputFD
to not-block?





    _______________________________________________________

File Attachments:


-------------------------------------------------------
Date: Fri 27 Aug 2010 09:16:39 PM GMT  Name:
performSelectorOnMmainThreadDeadlock.txt  Size: 4kB   By: jonathanosx
Backtrace of Deadlock
<http://savannah.gnu.org/bugs/download.php?file_id=21326>

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?30892>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/


_______________________________________________
Bug-gnustep mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/bug-gnustep

Reply via email to