|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
No idea for a fix from me, sorry. The tip about unsynchronized access sounds plausible, but as you note, all accesses to the map should be synchronized from the same monitor. If you can reproduce the bug, then there are various ways of proceeding with debugging, such as switching to a (strong) HashMap to see if the endless loop goes away; this would of course introduce a memory leak, but at least you would have narrowed down the problem.