| Summary: | Memory leaks in UML2Writer | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Modeling] M2T | Reporter: | Tatiana Fesenko <tatiana.fesenko> | ||||||
| Component: | Xpand | Assignee: | Karsten Thoms <karsten.thoms> | ||||||
| Status: | CLOSED FIXED | QA Contact: | |||||||
| Severity: | normal | ||||||||
| Priority: | P3 | CC: | karsten.thoms, sven.efftinge | ||||||
| Version: | 1.1.0 | Keywords: | contributed | ||||||
| Target Milestone: | M3 | Flags: | karsten.thoms:
juno+
|
||||||
| Hardware: | PC | ||||||||
| OS: | Mac OS X - Carbon (unsup.) | ||||||||
| Whiteboard: | |||||||||
| Attachments: |
|
||||||||
Created attachment 205609 [details]
Proposed patch
Patch is OK. Thanks! Bug resolved before Xpand 1.2 release date => Closing |
Created attachment 205608 [details] A sample project demonstrating this issue. Create a transformation that creates a UML model. Add reference to another model, e.g. PackageImport of UML Primitive Types library. "java.lang.OutOfMemoryError: Java heap space" will occur after some 100 iterations. The problem is that UML2Writer doesn't unload the resources after saving them in a file. That's why CacheAdapter.InverseCrossReferencer keeps the objects that are not in use any longer.