The fix for RT-13914: "Mac: Assertion failed: ([NSOpenGLContext currentContext] == [self openGLContext]), function -[GlassView3D begin] (detail) "
replaces lockFocus to lockFocusIfCanDraw and as result could lead to some extra rendering. This results in significant performance regressions (up to 20 fps)
for many benchmarks.

See Aurora results here:
 http://aurora.russia.sun.com/performance/faces/ChessBoard.xhtml?reportName=FX2-graphics-scrum&parameters=%5Bshownbenchmarks%5D%281%3D1%29%5Brefrelease%5D2.0.2%5Brefbuild%5D%3D+%2710085%27%5Brefjdkrelease%5D1.6.0_26%5Brelease%5D%28pr.product.productRelease+%3D+%272.0.2%27%29%5Bbuild%5D%28pr.product.build+%3D+%2710085%27%29OR%28pr.product.build+%3D+%2710086%27%29%5Bjdkrelease%5D%28jdk.product.productRelease+IS+NOT+NULL%29%5Bhwclass%5Dhost.machine.additionalInfo+%3D+%27Mac-Mid-Range%27&splitting=%5BX+axis%5DfxConf%2C+metricName%5BComplement%5Dbenchmark%2C+jdkBuild%2C+jdk%5BY+axis%5DbenchmarkName%2C+benchmarkConf%2C+fxRelease%2C+fxBuild%5BZ+axis%5Dos%2C+hwclass%2C+jdkRelease%2C+benchmarkSuite&reference=%5BOthers%5DfxRelease%2C+fxBuild%2C+jdkRelease%2C+jdkBuild%2C+jdk%2C+benchmarkSuite%2C+benchmarkName%2C+metricName%5BReference+Set%5Dbenchmark%2C+os%2C+benchmarkConf%2C+fxConf%2C+hwclass&mixReference=false&flags=&significance=empty&hideDataConfiguration=false&calculateSummary=false
&showSummaryExpanded=false&showSummaryContents=true&showComplementAttributes=false&compactTables=true&viewStyle=chessboard&filter=


According to the bug fixer it should be possible to fix the issue on Prism/Quantum level and as result not using lockFocusIfCanDraw which is slow.

Filing the bug to investigate it.