Closed GoogleCodeExporter closed 9 years ago
Original comment by nilsheu...@google.com
on 11 Mar 2013 at 9:39
Sorry for the delayed reply. Due to technical reasons we currently can not
deliver patches. As soon as this is fixed I will send you a patch for this bug.
Best regards,
Nils
Original comment by nilsheu...@google.com
on 13 Mar 2013 at 9:36
Original comment by nilsheu...@google.com
on 13 Mar 2013 at 9:37
I know it's not nice to bump an issue this way, but it's quite some time now.
At least an estimate about how long this "technical reason" will remain would
be nice.
Original comment by L783x...@gmail.com
on 27 Mar 2013 at 2:52
Ok, the "technical reason" is that we have to switch to another build system.
I'll try to adapt the build files and fix the bug within the next two weeks...
Original comment by nilsheu...@google.com
on 27 Mar 2013 at 4:24
Sorry for the late handling of this issue but finally I managed to investigate
your report. Unfortunately I can not really fix this. What happens is that the
JAVA VM runs out of memory while writing images of bigger graphs. The smaller
ones work fine. The responsible function is part of our external library, so I
just can report this bug and wait for a fix but this may take months.
Nevertheless I can give you some hints.
1. Choosing jpeg as output format seems a bit less memory consumptive.
2. You could increase the reserved VM memory
(http://www.zynamics.com/kb/kb0003.html)
3. Depending on the graph size and the reserved memory 1 and 2 will not really
help to export bigger graphs. The only way here is to select 'View' as clip
area. This should work always because it's actually just a screenshot of the
current view area.
Original comment by nilsheu...@google.com
on 17 Apr 2013 at 10:11
Original issue reported on code.google.com by
L783x...@gmail.com
on 3 Mar 2013 at 6:14