GNUstep - Bugs: bug #38980, NSConnection can cause thread...
bug #38980: NSConnection can cause thread deadlock
Submitter: | Michael Silva <msilvax28> | ||
Submitted: | Mon 13 May 2013 04:59:35 PM UTC | ||
Category: | Base/Foundation | Severity: | 3 - Normal |
Item Group: | Bug | Status: | Wont Fix |
Privacy: | Public | Assigned to: | None |
Open/Closed: | Closed |
Discussion locked!
Sun 12 Dec 2021 06:39:40 AM UTC, comment #2: |
Gregory John Casamento <gcasa> |
Thu 27 Jun 2013 06:56:08 AM UTC, comment #1: I wonder if there's any way to restructure locateLocalTarget to only hold one lock at a time? As long as it's holding two locks, it's hard to see how to completely avoid the possibility of deadlock. |
Richard Frith-Macdonald <CaS> |
Mon 13 May 2013 04:59:35 PM UTC, original submission:
There are cases in NSConnection when the use of NSRecursiveLocks between objects can lead to 2 threads deadlocking.
|
Michael Silva <msilvax28> |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Follow 3 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2021-12-12 | gcasa | Status | None | Wont Fix | |
Open/Closed | Open | Closed | |||
Discussion Lock | None | Locked |
Powered by Savane 3.13-02a9.
Corresponding source code
This "bug" appears to be theoretical. Has there been an instance of this? If so, open a bug on github for this.