On Dec 2, 2007, at 9:52 AM, Christiaan Hofman wrote:

>
>
> On Dec 2, 2007 5:46 PM, Adam R. Maxwell <[EMAIL PROTECTED]> wrote:
> I originally added enableMultipleThreads because I hit that exception
> during development.  Since I forgot to comment it, I removed it last
> May since it seemed unnecessary (using a similar argument to yours),
> tested it, and it worked fine.  We then released a new version and got
> a couple of exception reports (I was able to reproduce it).
>
> That may have been a side effect of the bug we had a while ago where  
> the  connection was accessed from the wrong thread. I'm quite sure  
> our connections don't need to be multi treaded. In fact, when that  
> exception occurs it's probably a sign of a bug in our code which we  
> should fix rather than ignore by allowing multiple threads to access  
> the connection.

Well, the exception occurred in our Rendezvous sharing system, which  
didn't have that bug as far as I know (and if sharing does have that  
proxy access problem it should assert in a debug build).  I agree with  
your premise: it shouldn't be required.  Empirical evidence suggests  
that it's necessary, either due to our bugs, Apple's bugs, or  
misdocumentation.

On the bug note, here's a great snippet from the 10.5 Foundation  
release notes:

Leaks in Distributed Objects plugged

Some leaks, and places where objects could leak if the timing was  
right, in Distributed Objects have been fixed in 10.5. This may mean  
that you may no longer get away with something you used to get away  
with due to the leak. Not retaining the root proxy you get from the  
connection, if you're going to hold onto it, seems to be a common  
pitfall.

-- 
adam

-------------------------------------------------------------------------
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell.  From the desktop to the data center, Linux is going
mainstream.  Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
_______________________________________________
Bibdesk-develop mailing list
Bibdesk-develop@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bibdesk-develop

Reply via email to