[jbosstools-issues] [JBoss JIRA] Issue Comment Edited: (JBDS-1577) using JBDS as updatesite on eclipse works, but causes outofmemory because of name change

[Nick Boldt (JIRA)]

    [ https://issues.jboss.org/browse/JBDS-1577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12586050#comment-12586050 ] 

Nick Boldt edited comment on JBDS-1577 at 3/4/11 11:50 AM:
-----------------------------------------------------------

Eclipse 3.6.2 / Helios SR2 uses very little memory in its eclipse.ini:

{color:red} -Xms40m -Xmx384m{color}

JBDS 4.0.0, however, sets much more reasonable minimums:

{color:green} -Xms512m -Xmx1024m{color}

If you tweak your eclipse.ini file with these values, does it work, or still throw OOM?

!JBDS-installed-into-Eclipse-memory-and-ini-settings.png!

      was (Author: nickboldt):
    Eclipse 3.6.2 / Helios SR2 uses very little memory in its eclipse.ini:

 -Xms40m -Xmx384m

JBDS 4.0.0, however, sets much more reasonable minimums:

 -Xms512m -Xmx1024m

If you tweak your eclipse.ini file with these values, does it work, or still throw OOM?

!JBDS-installed-into-Eclipse-memory-and-ini-settings.png!
  
> using JBDS as updatesite on eclipse works, but causes outofmemory because of name change
> ----------------------------------------------------------------------------------------
>
>                 Key: JBDS-1577
>                 URL: https://issues.jboss.org/browse/JBDS-1577
>             Project: Developer Studio (JBoss Developer Studio)
>          Issue Type: Bug
>          Components: updatesite
>    Affects Versions: 4.0.0.GA
>            Reporter: Max Rydahl Andersen
>            Assignee: Max Rydahl Andersen
>         Attachments: JBDS-installed-into-Eclipse-memory-and-ini-settings.png
>
>
> Not sure if this qualifies as a bug or a feature request but
> I noticed that if I use JBDS 4 updatesite against plain Eclipse things seem to work great
> until you restart (possible on the second restart) since then it suddenly has zero
> extra memory allocated.
> It only started working properly when using the jbdevstudio.app; thus my assumption is that
> eclipse.ini is ignored and jbdevstudio.ini is looked for instead but this file is nowhere
> to be found (except inside jbdevstudio.app)
> Would be good if we could handle this situation more gracefully since the shortcuts users
> uses still points to eclipse thus they will see it as JBDS running out of memory since when launching
> it says JBDS.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira