You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@directory.apache.org by David Parker <dp...@utica.edu> on 2019/12/04 16:00:31 UTC
Re: Directory Studio high memory usage
Hello,
After a few months without issues, I'm suddenly back to the same problem
again. I was in the middle of using Directory Studio with a few different
connections open, and suddenly it sort of froze and wouldn't save a change
I was making to a record. When I closed ADS and tried to open it again, I
got an error on the screen and the "java.lang.OutOfMemoryError: Java heap
space" exception in the log. This has now persisted across several
attempts to open the application.
I'm running Directory Studio 2.0.0.v20180908-M14 with OpenJDK 13 on Debian
10. I am using -Xms128m -Xmx512m as the heap sizes in my
ApacheDirectoryStudio.ini.
When I use -Xmx2048m it will start up and I can search, but I can't open
any records in the LDAP browser.
Any ideas or suggestions are greatly appreciated!
Thanks,
Dave
On Mon, Sep 30, 2019 at 4:54 PM David Parker <dp...@utica.edu> wrote:
> I suspect this may have been an issue with the Java version (although I
> don't know why). After upgrading from Java 8u161 to OpenJDK 13, I have not
> been able to reproduce the problem. Hopefully that turns out to be the fix!
>
> Thanks,
> Dave
>
> On Mon, Sep 30, 2019 at 4:39 PM David Parker <dp...@utica.edu> wrote:
>
>> Hello,
>>
>> I deleted my ~/.ApacheDirectoryStudio directory entirely, and started
>> from scratch. I added back my two LDAP connections (it's actually the same
>> directory with two different levels of privileges). My
>> ~/.ApacheDirectoryStudio is now 1.6 MB total. I still get the heap space
>> error on launch, using -Xms128m -Xmx512m.
>>
>> The schema for this LDAP directory hasn't really changed in several
>> years. The directory itself has grown in terms of the umber of records,
>> but the schema has remained the same. So why am I suddenly getting this
>> memory error when it was always fine before?
>>
>> Any help is greatly appreciated!
>>
>> Thanks!
>> Dave
>>
>>
>> On Mon, Sep 30, 2019 at 10:41 AM David Parker <dp...@utica.edu> wrote:
>>
>>> Hello,
>>>
>>> Thanks for the suggestions. Unfortunately, my entire
>>> ~/.ApacheDirectoryStudio directory is only 7 MB:
>>>
>>> $ du -h -d0 ~/.ApacheDirectoryStudio/
>>> 7.0M /home/dparker/.ApacheDirectoryStudio/
>>>
>>> The schemas are each around 500K and none of the logs are out of control.
>>>
>>> - Dave
>>>
>>> On Sat, Sep 28, 2019 at 1:49 PM Stefan Seelmann <ma...@stefan-seelmann.de>
>>> wrote:
>>>
>>>> Hi Dave,
>>>>
>>>> that's clearly not normal and it should launch with less than 500MB.
>>>>
>>>> One idea I have is maybe one of the server's schemas is so large? It's
>>>> cached on disk and loaded when Studio is launched. The cached schemas
>>>> are located in
>>>>
>>>> ~/.ApacheDirectoryStudio/.metadata/.plugins/org.apache.directory.studio.ldapbrowser.core
>>>>
>>>> There was also an issue with too large logfiles that were loaded during
>>>> startup (https://issues.apache.org/jira/browse/DIRSTUDIO-1148), maybe
>>>> you can check if that's the case:
>>>> du -h -d0 ~/.ApacheDirectoryStudio/
>>>> du -h -d1 ~/.ApacheDirectoryStudio/.metadata/.plugins
>>>>
>>>> Kind Regards,
>>>> Stefan
>>>>
>>>>
>>>> On 9/27/19 10:35 PM, David Parker wrote:
>>>> > Hello,
>>>> >
>>>> > I recently installed the most recent Directory Studio on my PC running
>>>> > Linux. Here are the release details:
>>>> >
>>>> > Apache Directory Studio
>>>> > Version: 2.0.0.v20180908-M14
>>>> > OS: Linux, v.4.19.0-6-amd64, x86_64 / gtk 2.24.32
>>>> > Java version: 1.8.0_161
>>>> >
>>>> > I was using an older version before without any problems. But with
>>>> the new
>>>> > version, I frequently get "java.lang.OutOfMemoryError: Java heap
>>>> space"
>>>> > errors when launching with the default memory settings, or even those
>>>> > recommended in the FAQ to resolve this error (-Xms128m -Xmx512m). I
>>>> have
>>>> > to bump the max heap up to 2 GB before it will launch. With
>>>> jconsole, I
>>>> > can see that it's using 1.6 GB of heap memory immediately after
>>>> launch.
>>>> >
>>>> > I only have 3 LDAP connections configured. It just doesn't seem like
>>>> > Directory Studio should require 2 GB of memory just to start up. Does
>>>> > anyone know why this is happening?
>>>> >
>>>> > Thanks,
>>>> > Dave
>>>> >
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: users-unsubscribe@directory.apache.org
>>>> For additional commands, e-mail: users-help@directory.apache.org
>>>>
>>>>
>>>
>>> --
>>> Dave Parker '11
>>> Database & Systems Administrator
>>> Utica College
>>> Integrated Information Technology Services
>>> (315) 792-3229
>>> Registered Linux User #408177
>>>
>>
>>
>> --
>> Dave Parker '11
>> Database & Systems Administrator
>> Utica College
>> Integrated Information Technology Services
>> (315) 792-3229
>> Registered Linux User #408177
>>
>
>
> --
> Dave Parker '11
> Database & Systems Administrator
> Utica College
> Integrated Information Technology Services
> (315) 792-3229
> Registered Linux User #408177
>
--
Dave Parker '11
Database & Systems Administrator
Utica College
Integrated Information Technology Services
(315) 792-3229
Registered Linux User #408177
Re: Directory Studio high memory usage
Posted by Stefan Seelmann <ma...@stefan-seelmann.de>.
On 1/6/20 10:25 AM, Stefan Seelmann wrote:
> yes, please open a Jira.
Done here: https://issues.apache.org/jira/browse/DIRSTUDIO-1247
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@directory.apache.org
For additional commands, e-mail: users-help@directory.apache.org
Re: Directory Studio high memory usage
Posted by Stefan Seelmann <ma...@stefan-seelmann.de>.
Hi David,
yes, please open a Jira.
Thanks,
Stefan
On 1/2/20 7:35 PM, David Parker wrote:
> I just wanted to follow up on this and say that several different issues I
> have been experiencing with Directory Studio can be immediately resolved by
> clearing my clipboard history. There are times when Directory Studio will
> stop opening records in the LDAP browser, or stop showing certain commands
> in the menu when I right-click on a search result. Clearing the clipboard
> fixes these issues without any need to restart the program.
>
> It's strange, because sometimes these things happen when I only have one
> small item copied to the clipboard. It doesn't really make sense why this
> would cause issues with Directory Studio. It also doesn't make sense that
> Directory Studio is looking at the clipboard in the first place. Should I
> open a bug report?
>
> On Tue, Dec 10, 2019 at 4:49 PM David Parker <dp...@utica.edu> wrote:
>
>> Hi Stefan,
>>
>> Great bit of detective work! That's an interesting bug. I'm not sure if
>> I had something large copied to my clipboard, but starting with an empty
>> clipboard does seem to help. I also added the memory arguments (-Xms128m
>> -Xmx512m) to the ApacheDirectoryStudio.ini file for 2.0.0-M13.
>>
>> Possibly related: I used the Glipper clipboard manager for many years, and
>> generally tried to maintain a neat clipboard by constantly removing entries
>> that weren't needed or had anything sensitive in them. Glipper was
>> deprecated and then removed in Debian 10, and I have yet to find an
>> alternative that is as robust and functional. So it's entirely possible
>> that I always had a smaller clipboard before, but now on Debian 10 I'm not
>> managing it like I did before, so it's probably a lot bigger.
>>
>> Thanks!
>>
>> On Tue, Dec 10, 2019 at 3:59 PM Stefan Seelmann <ma...@stefan-seelmann.de>
>> wrote:
>>
>>> Oh my, indeed, it looks like the ConnectionTransfer reads any (binary)
>>> data that's currently in the clipboard, that looks really wrong and
>>> dangerous.
>>>
>>>
>>> https://github.com/apache/directory-studio/blob/master/plugins/connection.ui/src/main/java/org/apache/directory/studio/connection/ui/dnd/ConnectionTransfer.java#L143
>>>
>>>
>>> On 12/10/19 9:36 PM, Stefan Seelmann wrote:
>>>> Hi Dave,
>>>>
>>>> the below OOM error looks weird. When it creates the "Connections" view
>>>> with all the actions it seems the paste action gets active and it reads
>>>> from your clipboard. If so I'd say that's a bug, I'll investigate.
>>>>
>>>> It it possible that there is a huge text in your clipboard you copied
>>>> before starting Studio? Can you try to clean it?
>>>>
>>>> Kind Regards,
>>>> Stefan
>>>>
>>>> On 12/10/19 7:44 PM, David Parker wrote:
>>>>> Hello,
>>>>>
>>>>> This is starting to get a bit frustrating. I continue to have
>>> heap-related
>>>>> crashes on startup, using both 2.0.0-M13 and 2.0.0-M14. I thought I
>>> had
>>>>> solved my problem with a clean install of M13 and Java 8u161, but a few
>>>>> days later, I'm back to the exact same issue. I did not have any of
>>> these
>>>>> problems until I got a new desktop PC and upgraded from Debian 9 to
>>> Debian
>>>>> 10. The LDAP schemas have not changed, and are not very big. I have
>>> no
>>>>> idea what's causing ADS to crash on startup with the heap error.
>>>>>
>>>>> Any help is greatly appreciated.
>>>>>
>>>>> Here's my ~/.ApacheDirectoryStudio/.metadata/.log from a recent launch
>>>>> attempt (this is launching 2.0.0-M13):
>>>>>
>>>>> java.lang.OutOfMemoryError: Java heap space
>>>>> at java.lang.StringCoding$StringDecoder.decode(StringCoding.java:149)
>>>>> at java.lang.StringCoding.decode(StringCoding.java:193)
>>>>> at java.lang.StringCoding.decode(StringCoding.java:254)
>>>>> at java.lang.String.<init>(String.java:546)
>>>>> at java.lang.String.<init>(String.java:566)
>>>>> at
>>>>>
>>> org.apache.directory.studio.connection.ui.dnd.ConnectionTransfer.nativeToJava(ConnectionTransfer.java:169)
>>>>> at org.eclipse.swt.dnd.Clipboard.getContents(Clipboard.java:320)
>>>>> at org.eclipse.swt.dnd.Clipboard.getContents(Clipboard.java:240)
>>>>> at
>>>>>
>>> org.apache.directory.studio.connection.ui.actions.PasteAction.getFromClipboard(PasteAction.java:290)
>>>>> at
>>>>>
>>> org.apache.directory.studio.connection.ui.actions.PasteAction.getConnectionsToPaste(PasteAction.java:181)
>>>>> at
>>>>>
>>> org.apache.directory.studio.connection.ui.actions.PasteAction.getText(PasteAction.java:62)
>>>>> at
>>>>>
>>> org.apache.directory.studio.connection.ui.actions.StudioActionProxy.<init>(StudioActionProxy.java:68)
>>>>> at
>>>>>
>>> org.apache.directory.studio.connection.ui.actions.StudioActionProxy.<init>(StudioActionProxy.java:94)
>>>>> at
>>>>>
>>> org.apache.directory.studio.connection.ui.actions.ConnectionViewActionProxy.<init>(ConnectionViewActionProxy.java:45)
>>>>> at
>>>>>
>>> org.apache.directory.studio.connection.ui.widgets.ConnectionActionGroup.<init>(ConnectionActionGroup.java:141)
>>>>> at
>>>>>
>>> org.apache.directory.studio.ldapbrowser.ui.views.connection.ConnectionViewActionGroup.<init>(ConnectionViewActionGroup.java:95)
>>>>> at
>>>>>
>>> org.apache.directory.studio.ldapbrowser.ui.views.connection.ConnectionView.createPartControl(ConnectionView.java:138)
>>>>> at
>>>>>
>>> org.eclipse.ui.internal.e4.compatibility.CompatibilityPart.createPartControl(CompatibilityPart.java:150)
>>>>
>>>>
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: users-unsubscribe@directory.apache.org
>>>> For additional commands, e-mail: users-help@directory.apache.org
>>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@directory.apache.org
>>> For additional commands, e-mail: users-help@directory.apache.org
>>>
>>>
>>
>> --
>> Dave Parker '11
>> Database & Systems Administrator
>> Utica College
>> Integrated Information Technology Services
>> (315) 792-3229
>> Registered Linux User #408177
>>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@directory.apache.org
For additional commands, e-mail: users-help@directory.apache.org
Re: Directory Studio high memory usage
Posted by David Parker <dp...@utica.edu>.
I just wanted to follow up on this and say that several different issues I
have been experiencing with Directory Studio can be immediately resolved by
clearing my clipboard history. There are times when Directory Studio will
stop opening records in the LDAP browser, or stop showing certain commands
in the menu when I right-click on a search result. Clearing the clipboard
fixes these issues without any need to restart the program.
It's strange, because sometimes these things happen when I only have one
small item copied to the clipboard. It doesn't really make sense why this
would cause issues with Directory Studio. It also doesn't make sense that
Directory Studio is looking at the clipboard in the first place. Should I
open a bug report?
On Tue, Dec 10, 2019 at 4:49 PM David Parker <dp...@utica.edu> wrote:
> Hi Stefan,
>
> Great bit of detective work! That's an interesting bug. I'm not sure if
> I had something large copied to my clipboard, but starting with an empty
> clipboard does seem to help. I also added the memory arguments (-Xms128m
> -Xmx512m) to the ApacheDirectoryStudio.ini file for 2.0.0-M13.
>
> Possibly related: I used the Glipper clipboard manager for many years, and
> generally tried to maintain a neat clipboard by constantly removing entries
> that weren't needed or had anything sensitive in them. Glipper was
> deprecated and then removed in Debian 10, and I have yet to find an
> alternative that is as robust and functional. So it's entirely possible
> that I always had a smaller clipboard before, but now on Debian 10 I'm not
> managing it like I did before, so it's probably a lot bigger.
>
> Thanks!
>
> On Tue, Dec 10, 2019 at 3:59 PM Stefan Seelmann <ma...@stefan-seelmann.de>
> wrote:
>
>> Oh my, indeed, it looks like the ConnectionTransfer reads any (binary)
>> data that's currently in the clipboard, that looks really wrong and
>> dangerous.
>>
>>
>> https://github.com/apache/directory-studio/blob/master/plugins/connection.ui/src/main/java/org/apache/directory/studio/connection/ui/dnd/ConnectionTransfer.java#L143
>>
>>
>> On 12/10/19 9:36 PM, Stefan Seelmann wrote:
>> > Hi Dave,
>> >
>> > the below OOM error looks weird. When it creates the "Connections" view
>> > with all the actions it seems the paste action gets active and it reads
>> > from your clipboard. If so I'd say that's a bug, I'll investigate.
>> >
>> > It it possible that there is a huge text in your clipboard you copied
>> > before starting Studio? Can you try to clean it?
>> >
>> > Kind Regards,
>> > Stefan
>> >
>> > On 12/10/19 7:44 PM, David Parker wrote:
>> >> Hello,
>> >>
>> >> This is starting to get a bit frustrating. I continue to have
>> heap-related
>> >> crashes on startup, using both 2.0.0-M13 and 2.0.0-M14. I thought I
>> had
>> >> solved my problem with a clean install of M13 and Java 8u161, but a few
>> >> days later, I'm back to the exact same issue. I did not have any of
>> these
>> >> problems until I got a new desktop PC and upgraded from Debian 9 to
>> Debian
>> >> 10. The LDAP schemas have not changed, and are not very big. I have
>> no
>> >> idea what's causing ADS to crash on startup with the heap error.
>> >>
>> >> Any help is greatly appreciated.
>> >>
>> >> Here's my ~/.ApacheDirectoryStudio/.metadata/.log from a recent launch
>> >> attempt (this is launching 2.0.0-M13):
>> >>
>> >> java.lang.OutOfMemoryError: Java heap space
>> >> at java.lang.StringCoding$StringDecoder.decode(StringCoding.java:149)
>> >> at java.lang.StringCoding.decode(StringCoding.java:193)
>> >> at java.lang.StringCoding.decode(StringCoding.java:254)
>> >> at java.lang.String.<init>(String.java:546)
>> >> at java.lang.String.<init>(String.java:566)
>> >> at
>> >>
>> org.apache.directory.studio.connection.ui.dnd.ConnectionTransfer.nativeToJava(ConnectionTransfer.java:169)
>> >> at org.eclipse.swt.dnd.Clipboard.getContents(Clipboard.java:320)
>> >> at org.eclipse.swt.dnd.Clipboard.getContents(Clipboard.java:240)
>> >> at
>> >>
>> org.apache.directory.studio.connection.ui.actions.PasteAction.getFromClipboard(PasteAction.java:290)
>> >> at
>> >>
>> org.apache.directory.studio.connection.ui.actions.PasteAction.getConnectionsToPaste(PasteAction.java:181)
>> >> at
>> >>
>> org.apache.directory.studio.connection.ui.actions.PasteAction.getText(PasteAction.java:62)
>> >> at
>> >>
>> org.apache.directory.studio.connection.ui.actions.StudioActionProxy.<init>(StudioActionProxy.java:68)
>> >> at
>> >>
>> org.apache.directory.studio.connection.ui.actions.StudioActionProxy.<init>(StudioActionProxy.java:94)
>> >> at
>> >>
>> org.apache.directory.studio.connection.ui.actions.ConnectionViewActionProxy.<init>(ConnectionViewActionProxy.java:45)
>> >> at
>> >>
>> org.apache.directory.studio.connection.ui.widgets.ConnectionActionGroup.<init>(ConnectionActionGroup.java:141)
>> >> at
>> >>
>> org.apache.directory.studio.ldapbrowser.ui.views.connection.ConnectionViewActionGroup.<init>(ConnectionViewActionGroup.java:95)
>> >> at
>> >>
>> org.apache.directory.studio.ldapbrowser.ui.views.connection.ConnectionView.createPartControl(ConnectionView.java:138)
>> >> at
>> >>
>> org.eclipse.ui.internal.e4.compatibility.CompatibilityPart.createPartControl(CompatibilityPart.java:150)
>> >
>> >
>> >
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: users-unsubscribe@directory.apache.org
>> > For additional commands, e-mail: users-help@directory.apache.org
>> >
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@directory.apache.org
>> For additional commands, e-mail: users-help@directory.apache.org
>>
>>
>
> --
> Dave Parker '11
> Database & Systems Administrator
> Utica College
> Integrated Information Technology Services
> (315) 792-3229
> Registered Linux User #408177
>
--
Dave Parker '11
Database & Systems Administrator
Utica College
Integrated Information Technology Services
(315) 792-3229
Registered Linux User #408177
Re: Directory Studio high memory usage
Posted by David Parker <dp...@utica.edu>.
Hi Stefan,
Great bit of detective work! That's an interesting bug. I'm not sure if I
had something large copied to my clipboard, but starting with an empty
clipboard does seem to help. I also added the memory arguments (-Xms128m
-Xmx512m) to the ApacheDirectoryStudio.ini file for 2.0.0-M13.
Possibly related: I used the Glipper clipboard manager for many years, and
generally tried to maintain a neat clipboard by constantly removing entries
that weren't needed or had anything sensitive in them. Glipper was
deprecated and then removed in Debian 10, and I have yet to find an
alternative that is as robust and functional. So it's entirely possible
that I always had a smaller clipboard before, but now on Debian 10 I'm not
managing it like I did before, so it's probably a lot bigger.
Thanks!
On Tue, Dec 10, 2019 at 3:59 PM Stefan Seelmann <ma...@stefan-seelmann.de>
wrote:
> Oh my, indeed, it looks like the ConnectionTransfer reads any (binary)
> data that's currently in the clipboard, that looks really wrong and
> dangerous.
>
>
> https://github.com/apache/directory-studio/blob/master/plugins/connection.ui/src/main/java/org/apache/directory/studio/connection/ui/dnd/ConnectionTransfer.java#L143
>
>
> On 12/10/19 9:36 PM, Stefan Seelmann wrote:
> > Hi Dave,
> >
> > the below OOM error looks weird. When it creates the "Connections" view
> > with all the actions it seems the paste action gets active and it reads
> > from your clipboard. If so I'd say that's a bug, I'll investigate.
> >
> > It it possible that there is a huge text in your clipboard you copied
> > before starting Studio? Can you try to clean it?
> >
> > Kind Regards,
> > Stefan
> >
> > On 12/10/19 7:44 PM, David Parker wrote:
> >> Hello,
> >>
> >> This is starting to get a bit frustrating. I continue to have
> heap-related
> >> crashes on startup, using both 2.0.0-M13 and 2.0.0-M14. I thought I had
> >> solved my problem with a clean install of M13 and Java 8u161, but a few
> >> days later, I'm back to the exact same issue. I did not have any of
> these
> >> problems until I got a new desktop PC and upgraded from Debian 9 to
> Debian
> >> 10. The LDAP schemas have not changed, and are not very big. I have no
> >> idea what's causing ADS to crash on startup with the heap error.
> >>
> >> Any help is greatly appreciated.
> >>
> >> Here's my ~/.ApacheDirectoryStudio/.metadata/.log from a recent launch
> >> attempt (this is launching 2.0.0-M13):
> >>
> >> java.lang.OutOfMemoryError: Java heap space
> >> at java.lang.StringCoding$StringDecoder.decode(StringCoding.java:149)
> >> at java.lang.StringCoding.decode(StringCoding.java:193)
> >> at java.lang.StringCoding.decode(StringCoding.java:254)
> >> at java.lang.String.<init>(String.java:546)
> >> at java.lang.String.<init>(String.java:566)
> >> at
> >>
> org.apache.directory.studio.connection.ui.dnd.ConnectionTransfer.nativeToJava(ConnectionTransfer.java:169)
> >> at org.eclipse.swt.dnd.Clipboard.getContents(Clipboard.java:320)
> >> at org.eclipse.swt.dnd.Clipboard.getContents(Clipboard.java:240)
> >> at
> >>
> org.apache.directory.studio.connection.ui.actions.PasteAction.getFromClipboard(PasteAction.java:290)
> >> at
> >>
> org.apache.directory.studio.connection.ui.actions.PasteAction.getConnectionsToPaste(PasteAction.java:181)
> >> at
> >>
> org.apache.directory.studio.connection.ui.actions.PasteAction.getText(PasteAction.java:62)
> >> at
> >>
> org.apache.directory.studio.connection.ui.actions.StudioActionProxy.<init>(StudioActionProxy.java:68)
> >> at
> >>
> org.apache.directory.studio.connection.ui.actions.StudioActionProxy.<init>(StudioActionProxy.java:94)
> >> at
> >>
> org.apache.directory.studio.connection.ui.actions.ConnectionViewActionProxy.<init>(ConnectionViewActionProxy.java:45)
> >> at
> >>
> org.apache.directory.studio.connection.ui.widgets.ConnectionActionGroup.<init>(ConnectionActionGroup.java:141)
> >> at
> >>
> org.apache.directory.studio.ldapbrowser.ui.views.connection.ConnectionViewActionGroup.<init>(ConnectionViewActionGroup.java:95)
> >> at
> >>
> org.apache.directory.studio.ldapbrowser.ui.views.connection.ConnectionView.createPartControl(ConnectionView.java:138)
> >> at
> >>
> org.eclipse.ui.internal.e4.compatibility.CompatibilityPart.createPartControl(CompatibilityPart.java:150)
> >
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@directory.apache.org
> > For additional commands, e-mail: users-help@directory.apache.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@directory.apache.org
> For additional commands, e-mail: users-help@directory.apache.org
>
>
--
Dave Parker '11
Database & Systems Administrator
Utica College
Integrated Information Technology Services
(315) 792-3229
Registered Linux User #408177
Re: Directory Studio high memory usage
Posted by Stefan Seelmann <ma...@stefan-seelmann.de>.
Oh my, indeed, it looks like the ConnectionTransfer reads any (binary)
data that's currently in the clipboard, that looks really wrong and
dangerous.
https://github.com/apache/directory-studio/blob/master/plugins/connection.ui/src/main/java/org/apache/directory/studio/connection/ui/dnd/ConnectionTransfer.java#L143
On 12/10/19 9:36 PM, Stefan Seelmann wrote:
> Hi Dave,
>
> the below OOM error looks weird. When it creates the "Connections" view
> with all the actions it seems the paste action gets active and it reads
> from your clipboard. If so I'd say that's a bug, I'll investigate.
>
> It it possible that there is a huge text in your clipboard you copied
> before starting Studio? Can you try to clean it?
>
> Kind Regards,
> Stefan
>
> On 12/10/19 7:44 PM, David Parker wrote:
>> Hello,
>>
>> This is starting to get a bit frustrating. I continue to have heap-related
>> crashes on startup, using both 2.0.0-M13 and 2.0.0-M14. I thought I had
>> solved my problem with a clean install of M13 and Java 8u161, but a few
>> days later, I'm back to the exact same issue. I did not have any of these
>> problems until I got a new desktop PC and upgraded from Debian 9 to Debian
>> 10. The LDAP schemas have not changed, and are not very big. I have no
>> idea what's causing ADS to crash on startup with the heap error.
>>
>> Any help is greatly appreciated.
>>
>> Here's my ~/.ApacheDirectoryStudio/.metadata/.log from a recent launch
>> attempt (this is launching 2.0.0-M13):
>>
>> java.lang.OutOfMemoryError: Java heap space
>> at java.lang.StringCoding$StringDecoder.decode(StringCoding.java:149)
>> at java.lang.StringCoding.decode(StringCoding.java:193)
>> at java.lang.StringCoding.decode(StringCoding.java:254)
>> at java.lang.String.<init>(String.java:546)
>> at java.lang.String.<init>(String.java:566)
>> at
>> org.apache.directory.studio.connection.ui.dnd.ConnectionTransfer.nativeToJava(ConnectionTransfer.java:169)
>> at org.eclipse.swt.dnd.Clipboard.getContents(Clipboard.java:320)
>> at org.eclipse.swt.dnd.Clipboard.getContents(Clipboard.java:240)
>> at
>> org.apache.directory.studio.connection.ui.actions.PasteAction.getFromClipboard(PasteAction.java:290)
>> at
>> org.apache.directory.studio.connection.ui.actions.PasteAction.getConnectionsToPaste(PasteAction.java:181)
>> at
>> org.apache.directory.studio.connection.ui.actions.PasteAction.getText(PasteAction.java:62)
>> at
>> org.apache.directory.studio.connection.ui.actions.StudioActionProxy.<init>(StudioActionProxy.java:68)
>> at
>> org.apache.directory.studio.connection.ui.actions.StudioActionProxy.<init>(StudioActionProxy.java:94)
>> at
>> org.apache.directory.studio.connection.ui.actions.ConnectionViewActionProxy.<init>(ConnectionViewActionProxy.java:45)
>> at
>> org.apache.directory.studio.connection.ui.widgets.ConnectionActionGroup.<init>(ConnectionActionGroup.java:141)
>> at
>> org.apache.directory.studio.ldapbrowser.ui.views.connection.ConnectionViewActionGroup.<init>(ConnectionViewActionGroup.java:95)
>> at
>> org.apache.directory.studio.ldapbrowser.ui.views.connection.ConnectionView.createPartControl(ConnectionView.java:138)
>> at
>> org.eclipse.ui.internal.e4.compatibility.CompatibilityPart.createPartControl(CompatibilityPart.java:150)
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@directory.apache.org
> For additional commands, e-mail: users-help@directory.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@directory.apache.org
For additional commands, e-mail: users-help@directory.apache.org
Re: Directory Studio high memory usage
Posted by Stefan Seelmann <ma...@stefan-seelmann.de>.
Hi Dave,
the below OOM error looks weird. When it creates the "Connections" view
with all the actions it seems the paste action gets active and it reads
from your clipboard. If so I'd say that's a bug, I'll investigate.
It it possible that there is a huge text in your clipboard you copied
before starting Studio? Can you try to clean it?
Kind Regards,
Stefan
On 12/10/19 7:44 PM, David Parker wrote:
> Hello,
>
> This is starting to get a bit frustrating. I continue to have heap-related
> crashes on startup, using both 2.0.0-M13 and 2.0.0-M14. I thought I had
> solved my problem with a clean install of M13 and Java 8u161, but a few
> days later, I'm back to the exact same issue. I did not have any of these
> problems until I got a new desktop PC and upgraded from Debian 9 to Debian
> 10. The LDAP schemas have not changed, and are not very big. I have no
> idea what's causing ADS to crash on startup with the heap error.
>
> Any help is greatly appreciated.
>
> Here's my ~/.ApacheDirectoryStudio/.metadata/.log from a recent launch
> attempt (this is launching 2.0.0-M13):
>
> java.lang.OutOfMemoryError: Java heap space
> at java.lang.StringCoding$StringDecoder.decode(StringCoding.java:149)
> at java.lang.StringCoding.decode(StringCoding.java:193)
> at java.lang.StringCoding.decode(StringCoding.java:254)
> at java.lang.String.<init>(String.java:546)
> at java.lang.String.<init>(String.java:566)
> at
> org.apache.directory.studio.connection.ui.dnd.ConnectionTransfer.nativeToJava(ConnectionTransfer.java:169)
> at org.eclipse.swt.dnd.Clipboard.getContents(Clipboard.java:320)
> at org.eclipse.swt.dnd.Clipboard.getContents(Clipboard.java:240)
> at
> org.apache.directory.studio.connection.ui.actions.PasteAction.getFromClipboard(PasteAction.java:290)
> at
> org.apache.directory.studio.connection.ui.actions.PasteAction.getConnectionsToPaste(PasteAction.java:181)
> at
> org.apache.directory.studio.connection.ui.actions.PasteAction.getText(PasteAction.java:62)
> at
> org.apache.directory.studio.connection.ui.actions.StudioActionProxy.<init>(StudioActionProxy.java:68)
> at
> org.apache.directory.studio.connection.ui.actions.StudioActionProxy.<init>(StudioActionProxy.java:94)
> at
> org.apache.directory.studio.connection.ui.actions.ConnectionViewActionProxy.<init>(ConnectionViewActionProxy.java:45)
> at
> org.apache.directory.studio.connection.ui.widgets.ConnectionActionGroup.<init>(ConnectionActionGroup.java:141)
> at
> org.apache.directory.studio.ldapbrowser.ui.views.connection.ConnectionViewActionGroup.<init>(ConnectionViewActionGroup.java:95)
> at
> org.apache.directory.studio.ldapbrowser.ui.views.connection.ConnectionView.createPartControl(ConnectionView.java:138)
> at
> org.eclipse.ui.internal.e4.compatibility.CompatibilityPart.createPartControl(CompatibilityPart.java:150)
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@directory.apache.org
For additional commands, e-mail: users-help@directory.apache.org
Re: Directory Studio high memory usage
Posted by David Parker <dp...@utica.edu>.
Hello,
This is starting to get a bit frustrating. I continue to have heap-related
crashes on startup, using both 2.0.0-M13 and 2.0.0-M14. I thought I had
solved my problem with a clean install of M13 and Java 8u161, but a few
days later, I'm back to the exact same issue. I did not have any of these
problems until I got a new desktop PC and upgraded from Debian 9 to Debian
10. The LDAP schemas have not changed, and are not very big. I have no
idea what's causing ADS to crash on startup with the heap error.
Any help is greatly appreciated.
Here's my ~/.ApacheDirectoryStudio/.metadata/.log from a recent launch
attempt (this is launching 2.0.0-M13):
!SESSION 2019-12-10 13:35:25.323
-----------------------------------------------
eclipse.buildId=unknown
java.version=1.8.0_161
java.vendor=Oracle Corporation
BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
Framework arguments: /studio-rcp/resources/icons/linux/studio.xpm
Command-line arguments: -os linux -ws gtk -arch x86_64
/studio-rcp/resources/icons/linux/studio.xpm
!ENTRY org.eclipse.ui 4 4 2019-12-10 13:35:31.996
!MESSAGE Could not create action delegate for id:
org.apache.directory.studio.ldapbrowser.ui.actions.GotoDnAction
!SUBENTRY 1 org.eclipse.ui 4 4 2019-12-10 13:35:31.996
!MESSAGE Internal plug-in action delegate error on creation.
!STACK 0
java.lang.NullPointerException
at
org.apache.directory.studio.ldapbrowser.ui.actions.GotoDnNavigateMenuAction.getSelectedConnection(GotoDnNavigateMenuAction.java:116)
at
org.apache.directory.studio.ldapbrowser.ui.actions.GotoDnNavigateMenuAction.isEnabled(GotoDnNavigateMenuAction.java:72)
at
org.apache.directory.studio.ldapbrowser.common.actions.BrowserAction.selectionChanged(BrowserAction.java:145)
at
org.eclipse.ui.internal.PluginAction.refreshEnablement(PluginAction.java:206)
at
org.eclipse.ui.internal.PluginAction.createDelegate(PluginAction.java:126)
at
org.eclipse.ui.internal.WWinPluginAction.refreshActionList(WWinPluginAction.java:167)
at org.eclipse.ui.plugin.AbstractUIPlugin$1.run(AbstractUIPlugin.java:482)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
at
org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:182)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4536)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4154)
at org.eclipse.swt.widgets.Display.release(Display.java:4206)
at org.eclipse.swt.graphics.Device.dispose(Device.java:266)
at org.apache.directory.studio.Application.start(Application.java:63)
at
org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:388)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:673)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:610)
at org.eclipse.equinox.launcher.Main.run(Main.java:1519)
at org.eclipse.equinox.launcher.Main.main(Main.java:1492)
!ENTRY org.eclipse.osgi 4 0 2019-12-10 13:35:32.010
!MESSAGE Application error
!STACK 1
java.lang.OutOfMemoryError: Java heap space
at java.lang.StringCoding$StringDecoder.decode(StringCoding.java:149)
at java.lang.StringCoding.decode(StringCoding.java:193)
at java.lang.StringCoding.decode(StringCoding.java:254)
at java.lang.String.<init>(String.java:546)
at java.lang.String.<init>(String.java:566)
at
org.apache.directory.studio.connection.ui.dnd.ConnectionTransfer.nativeToJava(ConnectionTransfer.java:169)
at org.eclipse.swt.dnd.Clipboard.getContents(Clipboard.java:320)
at org.eclipse.swt.dnd.Clipboard.getContents(Clipboard.java:240)
at
org.apache.directory.studio.connection.ui.actions.PasteAction.getFromClipboard(PasteAction.java:290)
at
org.apache.directory.studio.connection.ui.actions.PasteAction.getConnectionsToPaste(PasteAction.java:181)
at
org.apache.directory.studio.connection.ui.actions.PasteAction.getText(PasteAction.java:62)
at
org.apache.directory.studio.connection.ui.actions.StudioActionProxy.<init>(StudioActionProxy.java:68)
at
org.apache.directory.studio.connection.ui.actions.StudioActionProxy.<init>(StudioActionProxy.java:94)
at
org.apache.directory.studio.connection.ui.actions.ConnectionViewActionProxy.<init>(ConnectionViewActionProxy.java:45)
at
org.apache.directory.studio.connection.ui.widgets.ConnectionActionGroup.<init>(ConnectionActionGroup.java:141)
at
org.apache.directory.studio.ldapbrowser.ui.views.connection.ConnectionViewActionGroup.<init>(ConnectionViewActionGroup.java:95)
at
org.apache.directory.studio.ldapbrowser.ui.views.connection.ConnectionView.createPartControl(ConnectionView.java:138)
at
org.eclipse.ui.internal.e4.compatibility.CompatibilityPart.createPartControl(CompatibilityPart.java:150)
at
org.eclipse.ui.internal.e4.compatibility.CompatibilityView.createPartControl(CompatibilityView.java:143)
at
org.eclipse.ui.internal.e4.compatibility.CompatibilityPart.create(CompatibilityPart.java:340)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:55)
at
org.eclipse.e4.core.internal.di.InjectorImpl.processAnnotated(InjectorImpl.java:966)
at
org.eclipse.e4.core.internal.di.InjectorImpl.processAnnotated(InjectorImpl.java:931)
at
org.eclipse.e4.core.internal.di.InjectorImpl.inject(InjectorImpl.java:151)
at
org.eclipse.e4.core.internal.di.InjectorImpl.internalMake(InjectorImpl.java:375)
at org.eclipse.e4.core.internal.di.InjectorImpl.make(InjectorImpl.java:294)
at
org.eclipse.e4.core.contexts.ContextInjectionFactory.make(ContextInjectionFactory.java:162)
at
org.eclipse.e4.ui.internal.workbench.ReflectionContributionFactory.createFromBundle(ReflectionContributionFactory.java:105)
!ENTRY org.eclipse.e4.ui.workbench 4 0 2019-12-10 13:35:32.016
!MESSAGE
!STACK 0
java.lang.NullPointerException
at
org.eclipse.jface.resource.JFaceResources.getResources(JFaceResources.java:209)
at
org.eclipse.jface.resource.JFaceResources.getResources(JFaceResources.java:227)
at org.eclipse.ui.part.WorkbenchPart.dispose(WorkbenchPart.java:100)
at
org.apache.directory.studio.ldapbrowser.ui.views.browser.BrowserView.dispose(BrowserView.java:122)
at
org.eclipse.ui.internal.e4.compatibility.CompatibilityPart.invalidate(CompatibilityPart.java:237)
at
org.eclipse.ui.internal.e4.compatibility.CompatibilityPart.destroy(CompatibilityPart.java:403)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:55)
at
org.eclipse.e4.core.internal.di.InjectorImpl.processAnnotated(InjectorImpl.java:966)
at
org.eclipse.e4.core.internal.di.InjectorImpl.processAnnotated(InjectorImpl.java:931)
at
org.eclipse.e4.core.internal.di.InjectorImpl.disposed(InjectorImpl.java:426)
at org.eclipse.e4.core.internal.di.Requestor.disposed(Requestor.java:154)
at
org.eclipse.e4.core.internal.contexts.ContextObjectSupplier$ContextInjectionListener.update(ContextObjectSupplier.java:78)
at
org.eclipse.e4.core.internal.contexts.TrackableComputationExt.update(TrackableComputationExt.java:111)
at
org.eclipse.e4.core.internal.contexts.TrackableComputationExt.handleInvalid(TrackableComputationExt.java:74)
at
org.eclipse.e4.core.internal.contexts.EclipseContext.dispose(EclipseContext.java:176)
at
org.eclipse.e4.core.internal.contexts.EclipseContext.dispose(EclipseContext.java:161)
at
org.eclipse.e4.core.internal.contexts.EclipseContext.dispose(EclipseContext.java:161)
at
org.eclipse.e4.core.internal.contexts.EclipseContext.dispose(EclipseContext.java:161)
at
org.eclipse.e4.core.internal.contexts.EclipseContext.dispose(EclipseContext.java:161)
at
org.eclipse.e4.core.internal.contexts.osgi.EclipseContextOSGi.dispose(EclipseContextOSGi.java:106)
at
org.eclipse.e4.core.internal.contexts.osgi.EclipseContextOSGi.bundleChanged(EclipseContextOSGi.java:139)
at
org.eclipse.osgi.internal.framework.BundleContextImpl.dispatchEvent(BundleContextImpl.java:903)
at
org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
at
org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
at
org.eclipse.osgi.internal.framework.EquinoxEventPublisher.publishBundleEventPrivileged(EquinoxEventPublisher.java:213)
at
org.eclipse.osgi.internal.framework.EquinoxEventPublisher.publishBundleEvent(EquinoxEventPublisher.java:120)
at
org.eclipse.osgi.internal.framework.EquinoxEventPublisher.publishBundleEvent(EquinoxEventPublisher.java:112)
at
org.eclipse.osgi.internal.framework.EquinoxContainerAdaptor.publishModuleEvent(EquinoxContainerAdaptor.java:156)
at org.eclipse.osgi.container.Module.publishEvent(Module.java:476)
at org.eclipse.osgi.container.Module.doStop(Module.java:634)
at org.eclipse.osgi.container.Module.stop(Module.java:498)
at org.eclipse.osgi.container.SystemModule.stop(SystemModule.java:202)
at
org.eclipse.osgi.internal.framework.EquinoxBundle$SystemBundle$EquinoxSystemModule$1.run(EquinoxBundle.java:165)
at java.lang.Thread.run(Thread.java:748)
!ENTRY org.eclipse.e4.ui.workbench 4 0 2019-12-10 13:35:32.019
!MESSAGE
!STACK 0
java.lang.NullPointerException
at
org.apache.directory.studio.ldapbrowser.ui.views.connection.ConnectionView.dispose(ConnectionView.java:98)
at
org.eclipse.ui.internal.e4.compatibility.CompatibilityPart.invalidate(CompatibilityPart.java:237)
at
org.eclipse.ui.internal.e4.compatibility.CompatibilityPart.destroy(CompatibilityPart.java:403)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:55)
at
org.eclipse.e4.core.internal.di.InjectorImpl.processAnnotated(InjectorImpl.java:966)
at
org.eclipse.e4.core.internal.di.InjectorImpl.processAnnotated(InjectorImpl.java:931)
at
org.eclipse.e4.core.internal.di.InjectorImpl.disposed(InjectorImpl.java:426)
at org.eclipse.e4.core.internal.di.Requestor.disposed(Requestor.java:154)
at
org.eclipse.e4.core.internal.contexts.ContextObjectSupplier$ContextInjectionListener.update(ContextObjectSupplier.java:78)
at
org.eclipse.e4.core.internal.contexts.TrackableComputationExt.update(TrackableComputationExt.java:111)
at
org.eclipse.e4.core.internal.contexts.TrackableComputationExt.handleInvalid(TrackableComputationExt.java:74)
at
org.eclipse.e4.core.internal.contexts.EclipseContext.dispose(EclipseContext.java:176)
at
org.eclipse.e4.core.internal.contexts.EclipseContext.dispose(EclipseContext.java:161)
at
org.eclipse.e4.core.internal.contexts.EclipseContext.dispose(EclipseContext.java:161)
at
org.eclipse.e4.core.internal.contexts.EclipseContext.dispose(EclipseContext.java:161)
at
org.eclipse.e4.core.internal.contexts.EclipseContext.dispose(EclipseContext.java:161)
at
org.eclipse.e4.core.internal.contexts.osgi.EclipseContextOSGi.dispose(EclipseContextOSGi.java:106)
at
org.eclipse.e4.core.internal.contexts.osgi.EclipseContextOSGi.bundleChanged(EclipseContextOSGi.java:139)
at
org.eclipse.osgi.internal.framework.BundleContextImpl.dispatchEvent(BundleContextImpl.java:903)
at
org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
at
org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
at
org.eclipse.osgi.internal.framework.EquinoxEventPublisher.publishBundleEventPrivileged(EquinoxEventPublisher.java:213)
at
org.eclipse.osgi.internal.framework.EquinoxEventPublisher.publishBundleEvent(EquinoxEventPublisher.java:120)
at
org.eclipse.osgi.internal.framework.EquinoxEventPublisher.publishBundleEvent(EquinoxEventPublisher.java:112)
at
org.eclipse.osgi.internal.framework.EquinoxContainerAdaptor.publishModuleEvent(EquinoxContainerAdaptor.java:156)
at org.eclipse.osgi.container.Module.publishEvent(Module.java:476)
at org.eclipse.osgi.container.Module.doStop(Module.java:634)
at org.eclipse.osgi.container.Module.stop(Module.java:498)
at org.eclipse.osgi.container.SystemModule.stop(SystemModule.java:202)
at
org.eclipse.osgi.internal.framework.EquinoxBundle$SystemBundle$EquinoxSystemModule$1.run(EquinoxBundle.java:165)
at java.lang.Thread.run(Thread.java:748)
On Wed, Dec 4, 2019 at 11:00 AM David Parker <dp...@utica.edu> wrote:
> Hello,
>
> After a few months without issues, I'm suddenly back to the same problem
> again. I was in the middle of using Directory Studio with a few different
> connections open, and suddenly it sort of froze and wouldn't save a change
> I was making to a record. When I closed ADS and tried to open it again, I
> got an error on the screen and the "java.lang.OutOfMemoryError: Java heap
> space" exception in the log. This has now persisted across several
> attempts to open the application.
>
> I'm running Directory Studio 2.0.0.v20180908-M14 with OpenJDK 13 on Debian
> 10. I am using -Xms128m -Xmx512m as the heap sizes in my
> ApacheDirectoryStudio.ini.
>
> When I use -Xmx2048m it will start up and I can search, but I can't open
> any records in the LDAP browser.
>
> Any ideas or suggestions are greatly appreciated!
>
> Thanks,
> Dave
>
> On Mon, Sep 30, 2019 at 4:54 PM David Parker <dp...@utica.edu> wrote:
>
>> I suspect this may have been an issue with the Java version (although I
>> don't know why). After upgrading from Java 8u161 to OpenJDK 13, I have not
>> been able to reproduce the problem. Hopefully that turns out to be the fix!
>>
>> Thanks,
>> Dave
>>
>> On Mon, Sep 30, 2019 at 4:39 PM David Parker <dp...@utica.edu> wrote:
>>
>>> Hello,
>>>
>>> I deleted my ~/.ApacheDirectoryStudio directory entirely, and started
>>> from scratch. I added back my two LDAP connections (it's actually the same
>>> directory with two different levels of privileges). My
>>> ~/.ApacheDirectoryStudio is now 1.6 MB total. I still get the heap space
>>> error on launch, using -Xms128m -Xmx512m.
>>>
>>> The schema for this LDAP directory hasn't really changed in several
>>> years. The directory itself has grown in terms of the umber of records,
>>> but the schema has remained the same. So why am I suddenly getting this
>>> memory error when it was always fine before?
>>>
>>> Any help is greatly appreciated!
>>>
>>> Thanks!
>>> Dave
>>>
>>>
>>> On Mon, Sep 30, 2019 at 10:41 AM David Parker <dp...@utica.edu> wrote:
>>>
>>>> Hello,
>>>>
>>>> Thanks for the suggestions. Unfortunately, my entire
>>>> ~/.ApacheDirectoryStudio directory is only 7 MB:
>>>>
>>>> $ du -h -d0 ~/.ApacheDirectoryStudio/
>>>> 7.0M /home/dparker/.ApacheDirectoryStudio/
>>>>
>>>> The schemas are each around 500K and none of the logs are out of
>>>> control.
>>>>
>>>> - Dave
>>>>
>>>> On Sat, Sep 28, 2019 at 1:49 PM Stefan Seelmann <
>>>> mail@stefan-seelmann.de> wrote:
>>>>
>>>>> Hi Dave,
>>>>>
>>>>> that's clearly not normal and it should launch with less than 500MB.
>>>>>
>>>>> One idea I have is maybe one of the server's schemas is so large? It's
>>>>> cached on disk and loaded when Studio is launched. The cached schemas
>>>>> are located in
>>>>>
>>>>> ~/.ApacheDirectoryStudio/.metadata/.plugins/org.apache.directory.studio.ldapbrowser.core
>>>>>
>>>>> There was also an issue with too large logfiles that were loaded during
>>>>> startup (https://issues.apache.org/jira/browse/DIRSTUDIO-1148), maybe
>>>>> you can check if that's the case:
>>>>> du -h -d0 ~/.ApacheDirectoryStudio/
>>>>> du -h -d1 ~/.ApacheDirectoryStudio/.metadata/.plugins
>>>>>
>>>>> Kind Regards,
>>>>> Stefan
>>>>>
>>>>>
>>>>> On 9/27/19 10:35 PM, David Parker wrote:
>>>>> > Hello,
>>>>> >
>>>>> > I recently installed the most recent Directory Studio on my PC
>>>>> running
>>>>> > Linux. Here are the release details:
>>>>> >
>>>>> > Apache Directory Studio
>>>>> > Version: 2.0.0.v20180908-M14
>>>>> > OS: Linux, v.4.19.0-6-amd64, x86_64 / gtk 2.24.32
>>>>> > Java version: 1.8.0_161
>>>>> >
>>>>> > I was using an older version before without any problems. But with
>>>>> the new
>>>>> > version, I frequently get "java.lang.OutOfMemoryError: Java heap
>>>>> space"
>>>>> > errors when launching with the default memory settings, or even those
>>>>> > recommended in the FAQ to resolve this error (-Xms128m -Xmx512m). I
>>>>> have
>>>>> > to bump the max heap up to 2 GB before it will launch. With
>>>>> jconsole, I
>>>>> > can see that it's using 1.6 GB of heap memory immediately after
>>>>> launch.
>>>>> >
>>>>> > I only have 3 LDAP connections configured. It just doesn't seem like
>>>>> > Directory Studio should require 2 GB of memory just to start up.
>>>>> Does
>>>>> > anyone know why this is happening?
>>>>> >
>>>>> > Thanks,
>>>>> > Dave
>>>>> >
>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: users-unsubscribe@directory.apache.org
>>>>> For additional commands, e-mail: users-help@directory.apache.org
>>>>>
>>>>>
>>>>
>>>> --
>>>> Dave Parker '11
>>>> Database & Systems Administrator
>>>> Utica College
>>>> Integrated Information Technology Services
>>>> (315) 792-3229
>>>> Registered Linux User #408177
>>>>
>>>
>>>
>>> --
>>> Dave Parker '11
>>> Database & Systems Administrator
>>> Utica College
>>> Integrated Information Technology Services
>>> (315) 792-3229
>>> Registered Linux User #408177
>>>
>>
>>
>> --
>> Dave Parker '11
>> Database & Systems Administrator
>> Utica College
>> Integrated Information Technology Services
>> (315) 792-3229
>> Registered Linux User #408177
>>
>
>
> --
> Dave Parker '11
> Database & Systems Administrator
> Utica College
> Integrated Information Technology Services
> (315) 792-3229
> Registered Linux User #408177
>
--
Dave Parker '11
Database & Systems Administrator
Utica College
Integrated Information Technology Services
(315) 792-3229
Registered Linux User #408177