Uploaded image for project: 'Red Hat CodeReady Studio (devstudio)'
  1. Red Hat CodeReady Studio (devstudio)
  2. JBDS-1577

Installing JBDS into Eclipse 3.6 works, but runs out of memory

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 5.0.0.Beta3
    • 4.0.0.GA
    • updatesite
    • None

    Description

      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.

      Attachments

        Issue Links

          is related to

          Sub-task - The sub-task of the issue JBDS-2087 move all features from com.jboss.jbds.all (generated top-level product feature) to com.jboss.jbds.product.feature so that all of JBDS can be installed into Eclipse via a single feature

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. JBDS-1209 Add installation instruction documentation as downloadable artifact in the customer support portal JBDS software section

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

          Activity

            People

              nivologd@gmail.com Denis Golovin (Inactive)
              manderse@redhat.com Max Andersen
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: