Follow-up Comment #1, bug #39092 (project gnustep):
In this case, -[WOSessionTimeOutManager handleTimer:] locks the lock (via
SYNCHRONIZED(GSWApp)), and then -[WOApplication _discountTerminatedSession]
also tries to acquire the same lock.
I'm afraid I'm not familiar enough with the code to know what a good fix would
be. I'd prefer to remove the locking code from _discountTerminatedSession, if
it's truly an internal method and should always be called from within a locked
context (it could test -tryLock if it needs that). Obviously a recursive lock
also solves the problem but I'd be loathe to introduce that big a change.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?39092>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
_______________________________________________
Bug-gnustep mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/bug-gnustep
