[
https://issues.apache.org/jira/browse/DIRSTUDIO-658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12868801#action_12868801
]
Stefan Seelmann commented on DIRSTUDIO-658:
-------------------------------------------
I could reproduce this issue on linux.
I observed that it takes longer the more connections are defined in the
connections view. So I created some thread dumps with jstack while Studio is
shutting down. The result worries me: We call disconnect() for each connection
and that calls System.gc(). I'll try to remove at least the System.gc() call
because it is totally nonsense.
"main" prio=10 tid=0x0000000041164000 nid=0x865 waiting on condition
[0x00007fed487b0000]
java.lang.Thread.State: RUNNABLE
at java.lang.Runtime.gc(Native Method)
at java.lang.System.gc(System.java:926)
at
org.apache.directory.studio.connection.core.io.jndi.JNDIConnectionWrapper.disconnect(JNDIConnectionWrapper.java:243)
at
org.apache.directory.studio.connection.core.ConnectionCorePlugin.stop(ConnectionCorePlugin.java:157)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl$2.run(BundleContextImpl.java:840)
> Exiting Directory Studio consumes CPU for couple of minutes
> -----------------------------------------------------------
>
> Key: DIRSTUDIO-658
> URL: https://issues.apache.org/jira/browse/DIRSTUDIO-658
> Project: Directory Studio
> Issue Type: Bug
> Affects Versions: 1.5.2, 1.5.3
> Environment: Windows 7 64-bit, 6 GB RAM
> Reporter: Aleks M
> Priority: Minor
>
> When exiting Directory Studio it goes into some kind of "overdrive" and the
> process starts to consume 50% of my CPU, i.e. one entire core for 1,5-2,5
> minutes before quitting.
> Looking at the process using Process Explorer on the Threads tab it shows a
> thread with a start address of: MSVCR71.dll!_endthread+0x31 consuming all
> that CPU time.
> Any idea why it could be doing that?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
