There are some borders in the JavaScript iBench that are drawn with bezier path code. The allocation and deallocation of NSBezierPath is showing on the profile. We should fix that.
Created attachment 3368 [details] patch to use CoreGraphics directly instead of using NSBezierPath
I measured a 1% improvement on the benchmark with the patch.
Comment on attachment 3368 [details] patch to use CoreGraphics directly instead of using NSBezierPath CGContextStrokeLineSegments could potentially be even faster than this, at least when not filling the path.