Bugfix/3.4 renderer clipping and crash fix #494
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This Bugfix fixes the Polygon rendering of clipped Polygons and also extends the logic of clipping for circumstances to be more robust.
I also moved the clipping decision methods to the GeometryClipper to be easier readable.
Currently if a stroke contains a dasharray an a logical defect geometry (for example one point a million meter away from the rest of the points) the jdk renderer will either consume a extrem large ammount of time or in the worst case the jdk will crash.
As this situation is extreamly annoying i also created a testcase to prevent the clipper from missing this situation.
(So for example if the patch would be reversed the JUnit Testcase will catch the timeout and fail)