Re: lock issues - again

[Fred Kiefer]

As you probably know this message comes from the update method on NSMenu. There 
we validate all menu entries to decide whether the entry should be active or 
not. This specifically comes from a menu named „Windows“, most likely our 
windows menu, where all he active windows are listed. But NSMenu is only 
relevant as it catches the exception that gets thrown by NSDistributedLock. The 
best you could do is add a debugger breakpoint in the HANDLING code and print 
out the stack from there. As far as I remember there is also a way to print the 
stack of an exception directly from code, maybe Richard could help here.

That way you could see where and why the exception actually happens. But maybe 
you and Richard are already aware of that. in that case just ignore my mail.

Fred
 

> Am 23.11.2016 um 10:05 schrieb Riccardo Mottola <riccardo.mottola@libero.it>:
> 
> Hi,
> 
> lock issues continue to bite us. They are now minimized when starting up 
> applications and there was certainly an improvement, however.
> 
> Today I saw this  on OpenBSD/amd64, a recent platform and usually stable 
> where I rarely saw lock issues.
> 
> I saw this just on app startup:
> 
> 2016-11-23 09:32:01.485 DataBasin[40294:20592121212176] Error Occurred While 
> Updating Menu Windows: <NSException: 0x12ba0efdc5d0> NAME:NSGenericException 
> REASON:lock '/tmp/GNUstepSecure1000/NSMessagePort/names/lock' already broken 
> INFO:(null)
> 
> I restarted the application several other times, couldn't reproduce it. 
> DataBasin is a normal application, not a doc-based app and there is no code 
> that manipulates the menus. Thus I don't know what is updating and why it 
> breaks. So strange.
> 
> 
> Riccardo
> 
> 
> _______________________________________________
> Discuss-gnustep mailing list
> Discuss-gnustep@gnu.org
> https://lists.gnu.org/mailman/listinfo/discuss-gnustep