[OpenJDK 2D-Dev] RFR 8149338: JVM Crash caused by Marlin renderer not handling NaN coordinates
Jim Graham
james.graham at oracle.com
Mon Feb 8 23:11:56 UTC 2016
More information about the 2d-dev mailing list
Mon Feb 8 23:11:56 UTC 2016
- Previous message: [OpenJDK 2D-Dev] RFR 8149338: JVM Crash caused by Marlin renderer not handling NaN coordinates
- Next message: [OpenJDK 2D-Dev] RFR 8149338: JVM Crash caused by Marlin renderer not handling NaN coordinates
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Is there a reason why you reversed the calculations for the slope at line 374? ...jim On 2/8/16 1:22 PM, Laurent Bourgès wrote: > Phil & Jim, > > Please review a simple fix for a SEGV in Marlin renderer due to NaN > coordinates: > bug: https://bugs.openjdk.java.net/browse/JDK-8149338 > webrev: http://cr.openjdk.java.net/~lbourges/marlin/marlin-8149338.0/ > > Changes: > - addLine: use first / last Y crossings to compute edge min/max Y that > ensures consistency with edgeBuckets / edgeBucketCounts arrays in case > of NaN values: it is used in dispose() to reset these critical arrays > (pointer-like) => robust and consistent zero-fill > - minor cleanup in closePath() to avoid upscaling coordinates > - added crash test > > Cheers, > Laurent
- Previous message: [OpenJDK 2D-Dev] RFR 8149338: JVM Crash caused by Marlin renderer not handling NaN coordinates
- Next message: [OpenJDK 2D-Dev] RFR 8149338: JVM Crash caused by Marlin renderer not handling NaN coordinates
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the 2d-dev mailing list