]> source.dussan.org Git - xmlgraphics-fop.git/commit
projects / xmlgraphics-fop.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: b811e76) | patch
After chasing a phantom for hours, it looks like it's simply the big images being...
authorJeremias Maerki <jeremias@apache.org>
Thu, 25 Aug 2005 14:26:28 +0000 (14:26 +0000)
committerJeremias Maerki <jeremias@apache.org>
Thu, 25 Aug 2005 14:26:28 +0000 (14:26 +0000)
commit73aef5739f02e0d4fcaebe2d0b2d99d81bbb332a
tree51841694971080de146efefad40bbeaaa1f58eeetree | snapshot
parentb811e764d5bc71e3dc3c4ac8f7a43145aabe7df5commit | diff
After chasing a phantom for hours, it looks like it's simply the big images being generated that eat over 90% of the memory and at some point cause an OutOfMemoryError. Releasing the bitmaps a little sooner now which helps a little. "-Xmx256m" is still a good idea for BatchDiffer.
Haven't found any memory leaks inside FOP, since I fixed the image cache.

git-svn-id: https://svn.apache.org/repos/asf/xmlgraphics/fop/trunk@240079 13f79535-47bb-0310-9956-ffa450edef68
test/java/org/apache/fop/visual/BatchDiffer.java diff | blob | history
Apache XML Graphics FOP: https://github.com/apache/xmlgraphics-fop