Message11198
@Stefan Thanks for the comments. I did have the jstack -l output but didn't save it sorry. As for the file paths I will have a look at why.
About the deadlocks, are these likely to affect real uses, or do we just see them in the tests? If we are seeing them at all I guess that's a issue but wondered about real uses. After a 5 min glance at https://github.com/jythontools/jython/commit/b142d46c2968b32a1823e438cea41ccbc6ac2978 it looks like a good idea but as always with synchronization it's all about the detail. I will try to take a better look at that as well. Maybe I can recreate the situation with the debugger. I'm not sure if its a read-lock here, jstack can actually see the deadlock so hoping its a bit clearer. I think I had another test hang probably with a deadlock and jstack couldn't find that one so maybe there is a read-lock issue as well. Always tricky to debug! |
|
Date |
User |
Action |
Args |
2017-03-07 09:14:48 | jamesmudd | set | messageid: <1488878088.18.0.241914960266.issue2565@psf.upfronthosting.co.za> |
2017-03-07 09:14:48 | jamesmudd | set | recipients:
+ jamesmudd, darjus, stefan.richthofer |
2017-03-07 09:14:48 | jamesmudd | link | issue2565 messages |
2017-03-07 09:14:47 | jamesmudd | create | |
|