You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Nelson Bartley (JIRA)" <ji...@apache.org> on 2016/10/05 03:20:20 UTC
[jira] [Comment Edited] (DIRSTUDIO-1119) Group (cn) with over 1000
members crashes
[ https://issues.apache.org/jira/browse/DIRSTUDIO-1119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15547471#comment-15547471 ]
Nelson Bartley edited comment on DIRSTUDIO-1119 at 10/5/16 3:20 AM:
--------------------------------------------------------------------
Sorry for the delay,
I activated the heap view, and it's currently bouncing between 100M and 1592M while using 100% of one CPU thread. There is no network communication currently happening, so whatever it is doing is entirely internal.
I think I noted this before, but while this type of activity is taking place (it never stops), it cannot be cancelled.
In my Activity Monitor, Studio is occupying 1.57GB of memory without any compression. 41 threads, 320 ports.
was (Author: nbartley):
Sorry for the delay,
I activated the heap view, and it's currently bouncing between 100M and 1592M while using 100% of one CPU thread. There is no network communication currently happening, so whatever it is doing is entirely internal.
I think I noted this before, but while this type of activity is taking place (it never stops), it cannot be cancelled.
> Group (cn) with over 1000 members crashes
> -----------------------------------------
>
> Key: DIRSTUDIO-1119
> URL: https://issues.apache.org/jira/browse/DIRSTUDIO-1119
> Project: Directory Studio
> Issue Type: Bug
> Affects Versions: 2.0.0-M10 (2.0.0.v20151221-M10)
> Environment: Mac OS/ Java 8u102
> Reporter: Nelson Bartley
>
> When opening a group object (cn) with over 1000 memberuid entries, the application locks, refuses to cancel the activity, and requires a forced quit.
> Note, this does not affect a list of users, just elements within a cn.
> If more details are required, please let me know, I can always reproduce this bug.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)