Details

    • Type: Bug Bug
    • Status: Resolved Resolved
    • Priority: Critical Critical
    • Resolution: Complete
    • Affects Version/s: 3.0.0.RELEASE
    • Fix Version/s: 3.1.0.RELEASE
    • Component/s: None
    • Labels:
      None

      Description

      some people are observing a slowdown in general, but even starting STS/GGTS up with a fresh workspace takes minutes for them.

      (see: http://forum.springsource.org/showthread.php?129319-STS-3-0-(Really-Eclipse-Juno)-is-slow)

      This issue is to analyze and hopefully fix these problems.

        Activity

        Hide
        Andrew Eisenberg (c) added a comment -

        Hi all,

        Thanks for your comments on the performance issues of STS 3.0.0 on Eclipse 4.2. We're aware of the issues and we are currently discussing the best way to move forward.

        Show
        Andrew Eisenberg (c) added a comment - Hi all, Thanks for your comments on the performance issues of STS 3.0.0 on Eclipse 4.2. We're aware of the issues and we are currently discussing the best way to move forward.
        Hide
        Garth D. added a comment -

        +1 for STS3.0 on Eclipse 4.2 being unusable on OSX...

        <Antidotal>
        I think there is something wrong with e4.2 corrupting workspace metadata.

        It seems I get about two start-ups with a workspace before STS3.0e4.2 can no longer get past "loading workbench" stage and I have to Force Quit STS. At that point my only option is to delete the workspace, recreate it blank and start reimporting projects (@!#$@#!%$#@).

        When I first loaded up the workspace, I noticed it would always corrupt the metadata if I deleted a project from the newly created workspace and restarted, but it happens even when you don't delete any projects...
        </Antidotal>

        Anyway, I agree that the e4.2 release on OSX is putting STS in a terrible light, I would suggest pulling the release or replacing it with that e3.7 build.

        @Lari thanks for the links to the e3.7 based build... I'm pulling down http://download.springsource.com/release/STS/3.0.0/dist/e3.7/spring-tool-suite-3.0.0.RELEASE-e3.7-macosx-cocoa-installer.dmg and I'm going to give that a try shortly.

        Show
        Garth D. added a comment - +1 for STS3.0 on Eclipse 4.2 being unusable on OSX... <Antidotal> I think there is something wrong with e4.2 corrupting workspace metadata. It seems I get about two start-ups with a workspace before STS3.0e4.2 can no longer get past "loading workbench" stage and I have to Force Quit STS. At that point my only option is to delete the workspace, recreate it blank and start reimporting projects (@!#$@#!%$#@). When I first loaded up the workspace, I noticed it would always corrupt the metadata if I deleted a project from the newly created workspace and restarted, but it happens even when you don't delete any projects... </Antidotal> Anyway, I agree that the e4.2 release on OSX is putting STS in a terrible light, I would suggest pulling the release or replacing it with that e3.7 build. @Lari thanks for the links to the e3.7 based build... I'm pulling down http://download.springsource.com/release/STS/3.0.0/dist/e3.7/spring-tool-suite-3.0.0.RELEASE-e3.7-macosx-cocoa-installer.dmg and I'm going to give that a try shortly.
        Hide
        Martin Lippert (c) added a comment -

        We have Eclipse 3.8-based builds now up and running for STS 3.1.0.M1 and beyond. Can you try those Eclipse-3.8-based builds to see if they solve your issues as well? We heart many positive things about 3.8-based builds and will therefore publish build STS 3.1.0 on Eclipse 3.8 (in addition to 4.2) by default.

        Show
        Martin Lippert (c) added a comment - We have Eclipse 3.8-based builds now up and running for STS 3.1.0.M1 and beyond. Can you try those Eclipse-3.8-based builds to see if they solve your issues as well? We heart many positive things about 3.8-based builds and will therefore publish build STS 3.1.0 on Eclipse 3.8 (in addition to 4.2) by default.
        Hide
        Garth D. added a comment -

        @Martin both the 3.1.0M1/e3.8 and 3.0.0/e3.7 have no problems opening up the workspace that 3.0.0/e4.2 deadlocks opening on start-up, both of the non-4.2 builds "feel" quite a bit snappier too. This is on a MBA 11.6 2011 / OSX 10.8.1.

        Show
        Garth D. added a comment - @Martin both the 3.1.0M1/e3.8 and 3.0.0/e3.7 have no problems opening up the workspace that 3.0.0/e4.2 deadlocks opening on start-up, both of the non-4.2 builds "feel" quite a bit snappier too. This is on a MBA 11.6 2011 / OSX 10.8.1.
        Hide
        Martin Lippert (c) added a comment -

        Good to hear that the 3.1..M1 on e3.8 works as expected. Please feel free to take a thread dump for the e4.2 version when it deadlocks or hangs (using jps and jstack) and attach that to this item. Would be interesting to see what caused the deadlock in your case exactly. Thanks in advance!!!

        Show
        Martin Lippert (c) added a comment - Good to hear that the 3.1..M1 on e3.8 works as expected. Please feel free to take a thread dump for the e4.2 version when it deadlocks or hangs (using jps and jstack) and attach that to this item. Would be interesting to see what caused the deadlock in your case exactly. Thanks in advance!!!

          People

          • Assignee:
            Andrew Eisenberg (c)
            Reporter:
            Martin Lippert (c)
          • Votes:
            1 Vote for this issue
            Watchers:
            6 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:
              First Response Date: