directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefan Seelmann (JIRA)" <>
Subject [jira] Commented: (DIRSTUDIO-658) Exiting Directory Studio consumes CPU for couple of minutes
Date Tue, 18 May 2010 19:31:43 GMT


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(
	at org.eclipse.osgi.framework.internal.core.BundleContextImpl$

> Exiting Directory Studio consumes CPU for couple of minutes
> -----------------------------------------------------------
>                 Key: DIRSTUDIO-658
>                 URL:
>             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.

View raw message