[
https://issues.apache.org/jira/browse/IVY-598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12523128
]
Colin Fleming commented on IVY-598:
-----------------------------------
Sorry, I spoke too soon. It's not actually deadlocked, it's spinning:
PID COMMAND %CPU TIME #TH #PRTS #MREGS RPRVT RSHRD RSIZE VSIZE
1144 top 6.9% 0:23.31 1 18 20 3.09M 424K 4.90M 27.0M
1105 mdimport 0.0% 0:00.08 3 60 44 788K 2.84M 2.48M 38.7M
1082 java 100.1% 12:02.72 12 >>> 218 154M 1.04M 116M 286M
1045 mdimport 0.0% 0:05.17 4 61 63 1.16M 3.05M 3.76M 39.3M
> ivy:info locks up
> -----------------
>
> Key: IVY-598
> URL: https://issues.apache.org/jira/browse/IVY-598
> Project: Ivy
> Issue Type: Bug
> Components: Ant
> Affects Versions: 2.0.0-alpha-2
> Environment: OSX 10.4.10, JDK 1.5.0_07
> Reporter: Colin Fleming
> Priority: Critical
> Attachments: debug.output.txt, threaddump.txt, threaddump2.txt,
> threaddump3.txt
>
>
> Occasionally Ivy seems to deadlock, and something that I've changed in our
> project suddenly makes it happen all the time. This is an urgent issue for
> us, it used to only affect me from time to time but suddenly it's frequently
> happening to most people in our project. It appears to lock up loading
> classes during an ivy:info. I can't break out with a Ctrl-C, I have to kill
> -9 the process from another terminal. I've attached three thread dumps from
> different times it's happened plus the debug output of one run of the
> ivy:info task (the run associated with threaddump3, in case it helps). This
> is almost 100% reproducible for me now, which unfortunately means I can build
> almost 0% of the time :(
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
