Re: [Jts-topo-suite-user] Does JTS 1.12 have any issues with increased heap usage at JDK 1.7?

[Jody G. <jod...@gm...>]

You did not change from a 32-bit JRE to a 64-bit JRE did you? That is the
easiest way to require more memory when upgrading Java.

You may also want to check for changes to the memory model, although I
think the unification of pergen and heap has been put off until Java 8.

Jody Garnett


On Thu, May 8, 2014 at 12:23 PM, Robert Justice <rju...@cl...>wrote:

> One of our customers is calling JTS libraries out of a Hive UDF and
> noticed a pretty dramatic jump of heap memory usage between JDK 1.6 and JDK
> 1.7.   We bumped up heap and added some CMS GC options to help, but were
> curious if anyone else had experienced any problems.
> I noticed 1.13 is out, does that help with heap usage?
>
> Exception
> --------------
> Caused by: java.lang.OutOfMemoryError: GC overhead limit exceeded
> at
> com.vividsolutions.jts.geomgraph.EdgeEndStar.<init>(EdgeEndStar.java:58)
> at
> com.vividsolutions.jts.geomgraph.DirectedEdgeStar.<init>(DirectedEdgeStar.java:60)
>
> at
> com.vividsolutions.jts.operation.overlay.OverlayNodeFactory.createNode(OverlayNodeFactory.java:54)
>
> at com.vividsolutions.jts.geomgraph.NodeMap.addNode(NodeMap.java:76)
> at com.vividsolutions.jts.geomgraph.NodeMap.add(NodeMap.java:101)
> at com.vividsolutions.jts.geomgraph.PlanarGraph.add(PlanarGraph.java:107)
> at
> com.vividsolutions.jts.geomgraph.PlanarGraph.addEdges(PlanarGraph.java:137)
> at
> com.vividsolutions.jts.operation.buffer.BufferBuilder.buffer(BufferBuilder.java:152)
>
> at
> com.vividsolutions.jts.operation.buffer.BufferOp.bufferFixedPrecision(BufferOp.java:341)
>
> at
> com.vividsolutions.jts.operation.buffer.BufferOp.bufferReducedPrecision(BufferOp.java:329)
>
> at
> com.vividsolutions.jts.operation.buffer.BufferOp.bufferReducedPrecision(BufferOp.java:293)
>
> at
> com.vividsolutions.jts.operation.buffer.BufferOp.computeGeometry(BufferOp.java:285)
>
> at
> com.vividsolutions.jts.operation.buffer.BufferOp.getResultGeometry(BufferOp.java:272)
>
> at
> com.vividsolutions.jts.operation.buffer.BufferOp.bufferOp(BufferOp.java:148)
>
> at com.vividsolutions.jts.geom.Geometry.buffer(Geometry.java:1157)
>
> Exception
> --------------
> Caused by: java.lang.OutOfMemoryError: Java heap space
> at
> com.vividsolutions.jts.geomgraph.EdgeIntersectionList.<init>(EdgeIntersectionList.java:49)
>
> at com.vividsolutions.jts.geomgraph.Edge.<init>(Edge.java:69)
> at
> com.vividsolutions.jts.operation.buffer.BufferBuilder.computeNodedEdges(BufferBuilder.java:196)
>
> at
> com.vividsolutions.jts.operation.buffer.BufferBuilder.buffer(BufferBuilder.java:150)
>
> at
> com.vividsolutions.jts.operation.buffer.BufferOp.bufferFixedPrecision(BufferOp.java:341)
>
> at
> com.vividsolutions.jts.operation.buffer.BufferOp.bufferReducedPrecision(BufferOp.java:329)
>
> at
> com.vividsolutions.jts.operation.buffer.BufferOp.bufferReducedPrecision(BufferOp.java:293)
>
> at
> com.vividsolutions.jts.operation.buffer.BufferOp.computeGeometry(BufferOp.java:285)
>
> at
> com.vividsolutions.jts.operation.buffer.BufferOp.getResultGeometry(BufferOp.java:272)
>
> at
> com.vividsolutions.jts.operation.buffer.BufferOp.bufferOp(BufferOp.java:148)
>
> at com.vividsolutions.jts.geom.Geometry.buffer(Geometry.java:1157)
> at
>
> --
> Thanks,
> ---
> Robert Justice
>
>
> ------------------------------------------------------------------------------
> Is your legacy SCM system holding you back? Join Perforce May 7 to find
> out:
> &#149; 3 signs your SCM is hindering your productivity
> &#149; Requirements for releasing software faster
> &#149; Expert tips and advice for migrating your SCM now
> http://p.sf.net/sfu/perforce
> _______________________________________________
> Jts-topo-suite-user mailing list
> Jts...@li...
> https://lists.sourceforge.net/lists/listinfo/jts-topo-suite-user
>
>