GWT Designer -- GC overhead limit exceeded

[Thad]

I part of my job I dislike the most is laying out HTML. As such I have a love-hate relationship with GWT Designer. While it makes some things easier, in many more ways it's just plain maddening.

Currently my chief gripe is how GWT Designer keeps crashing Eclipse. Even when I'm not getting errors back on switching from XML Source view to Design view, the progress bar will stop and, after some wait, I receive an error dialog:

Designer [1.3.0.r37x201202021417.201206281156]: GC overhead limit exceeded

GC overhead limit exceeded

When I close this, I get a crash dialog and must close Eclipse.

I am running Eclipse IDE for Java Developers, Version: Indigo Service Release 2, Build id: 20120216-1857 on openSUSE 12.1 with the latest Java 1.6 from Sun (although this has been a problem with earlier versions of openSUSE, Java, Eclipse, and GWT Designer).

Is anyone else experiencing this problem?

[Philippe Lhoste]

On 28/06/2012 22:33, Thad wrote:
> I part of my job I dislike the most is laying out HTML. As such I have a love-hate
> relationship with GWT Designer. While it makes some things easier, in many more ways it's
> just plain maddening.
>
> Currently my chief gripe is how GWT Designer keeps crashing Eclipse. Even when I'm

> /not/ getting errors back on switching from XML Source view to Design view, the progress

> bar will stop and, after some wait, I receive an error dialog:
>
> Designer [1.3.0.r37x201202021417.201206281156]: GC overhead limit exceeded
> GC overhead limit exceeded
>
>
> When I close this, I get a crash dialog and must close Eclipse.
>
> I am running Eclipse IDE for Java Developers, Version: Indigo Service Release 2, Build id:
> 20120216-1857 on openSUSE 12.1 with the latest Java 1.6 from Sun (although this has been a
> problem with earlier versions of openSUSE, Java, Eclipse, and GWT Designer).
>
> Is anyone else experiencing this problem?

I don't use GWT Designer (I am OK with HTML layout...) but when you have "GC overhead
limit exceeded", most advices I saw was to increase the max memory (the Xmx parameter).
For Eclipse, you do this in the eclipse.ini file at the root of the Eclipse configuration
(sorry if I state evidences).
If your computer allows it, it is worth trying.

--
Philippe Lhoste
-- (near) Paris -- France
-- http://Phi.Lho.free.fr
-- -- -- -- -- -- -- -- -- -- -- -- -- --