Community
Participate
Working Groups
Created attachment 183638 [details] screenshot showing the different numbers I maintain a set of bundles for Orbit. There are bundles which come with a significant amount of files (a few thousand class files as well as source files). It was impossible to commit those projects at once with Eclipse 3.6.1. Whenever I right clicked a project and selected "Commit" the commit dialog just didn't appear at all. No error was logged. As a workaround, I always had to use the Synchronize View and commit the project in multiple smaller chunks. Now in 3.7M3 the commit dialog appears. However, Eclipse dies with an OutOfMemoryException during the commit. Looking at the Windows Task Manager showed ~1.8GB of consumed memory. I therefor started Eclipse with -XX:+HeapDumpOnOutOfMemoryError and restarted the commit. I also took the chance to monitor the JVM more closely and take heap dumps. Now the weird part started. The memory numbers reported by the Windows Task Manager are an order of magnitude higher than what the JVM thinks it is using. The JVM heap dumps aren't helpful at all. They reflect the JVM numbers, i.e. a heap dump is about 200MB in size although the task manager still reports 1.7GB. Any thoughts?
Note, I'm not sure what can be done here. The Java heap looks small. The only thing I can imagine is that a lot of objects (eg. byte arrays?) are created which could probably be improved by reusing a buffer? But I don't know the CVS internals. Anyway, I just thought it might be worth reporting. The commit when through after the 4th or 5th attempt.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
