Message10705

Author	nickmbailey
Recipients	nickmbailey, stefan.richthofer, zyasoft
Date	2016-02-03.19:52:23
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1454529143.79.0.611070067848.issue2457@psf.upfronthosting.co.za>
In-reply-to

Content
I'm still leaning towards removing synchronization on a class object when multiple instances of that object (in multiple threads) and the finalizer all lock on it. I think the solution we just applied for this solves the issue in http://bugs.jython.org/issue2280 by not having any locking in Closer.java. So I think in this issue we can safely remove the class synchronization.

I'm still leaning towards removing synchronization on a class object when multiple instances of that object (in multiple threads) and the finalizer all lock on it. I *think* the solution we just applied for this solves the issue in http://bugs.jython.org/issue2280 by not having any locking in Closer.java. So I think in this issue we can safely remove the class synchronization.

History
Date	User	Action	Args
2016-02-03 19:52:23	nickmbailey	set	messageid: <1454529143.79.0.611070067848.issue2457@psf.upfronthosting.co.za>
2016-02-03 19:52:23	nickmbailey	set	recipients: + nickmbailey, zyasoft, stefan.richthofer
2016-02-03 19:52:23	nickmbailey	link	issue2457 messages
2016-02-03 19:52:23	nickmbailey	create