locationtech
Java multipoint buffer memory overflow, what's a good way
After recognizing the map, our program generates multiple points, and then buffer the memory overflow. After I debug the single point buffer, it is OK, and after simplification, the memory overflow will occur again. If single point buffer and simplification are used, the final result seems to be wrong. What's a good method
The following is the detailed code： BufferOp bufOp = new BufferOp(geometry); bufOp.setEndCapStyle(BufferParameters.CAP_SQUARE); Geometry geometryBuffer = bufOp.getResultGeometry(bufferDistance);
Geometry geometryBufferSimplify = VWSimplifier.simplify(geometryBuffer, 0.05);
The coordinateArray is more than 400000
As would input data that reproduces the problem. The description of the problem isn't clear to me at all.
On Tue, Oct 11, 2022 at 7:26 AM Mark Prins @.***> wrote:
the full stack trace would be helpful analysing your problem
— Reply to this email directly, view it on GitHub https://github.com/locationtech/jts/issues/913#issuecomment-1274778417, or unsubscribe https://github.com/notifications/unsubscribe-auth/AA25SXJQJMNFAOMZZZWYCPTWCV2JZANCNFSM6AAAAAARCHUI6I . You are receiving this because you are subscribed to this thread.Message ID: @.***>
Your report is still missing key information for debugging and/or analysis, but the essence is you need more memory for your program; this may help: https://www.baeldung.com/java-gc-overhead-limit-exceeded
Thank you for your answer. I adjusted the jvm memory size to 5G in the local idea Exe program observation, to bufOp The getResultGeometry (bufferDistance) line of code will be gc. It is reasonable to say that the size of the jvm is enough. Why is gc still needed?
