http://gwt-code-reviews.appspot.com/1517803/diff/5002/dev/core/src/com/google/gwt/dev/javac/CompiledClass.java
File dev/core/src/com/google/gwt/dev/javac/CompiledClass.java (right):

http://gwt-code-reviews.appspot.com/1517803/diff/5002/dev/core/src/com/google/gwt/dev/javac/CompiledClass.java#newcode57
dev/core/src/com/google/gwt/dev/javac/CompiledClass.java:57:
copyCc.initUnit(newUnit);


This fixes the problem with writing out 2 units every time we write out
a CachedCompilation unit that has been copied from another compilation
unit.

In my first attempt to fix, I repointed this, but the CompiledClass was
shared between two different units.
Now that it the CompiledClasses are copied, once we write out the cached
cmopilation unit and throw away the reference, the old compilation
unit's CompiledClasses won't keep the cached compilation unit memroy
alive.

http://gwt-code-reviews.appspot.com/1517803/

--
http://groups.google.com/group/Google-Web-Toolkit-Contributors

Reply via email to