The only frame type that uses SVG markers is nsSVGPathGeometryFrame. We should stop wastefully creating nsSVGMarkerProperty objects for other frame types.
Attachment #676899 - Flags: review?(roc) → review+
Version: 17 Branch → Trunk
Looking forward to tmrw when it lands to mozilla-central :) and i can reenable fuzzing markers :)
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla19
Comment on attachment 676899 [details] [diff] [review] patch We should take this on branches.
status-firefox17: --- → affected
status-firefox18: --- → affected
status-firefox19: --- → fixed
tracking-firefox17: --- → +
tracking-firefox18: --- → +
Comment on attachment 676899 [details] [diff] [review] patch As per email, go ahead with uplift on this, we know the risk to be low. I'm clearing the ESR17 flag since we'll get this on the first ESR17 by virtue of it getting on mozilla-beta now (17).
status-firefox17: affected → fixed
status-firefox18: affected → fixed
Jonathan: is this fixing a long-standing issue or is this fixing a regression in Firefox 17?
The patch fixes a long-standing issue in the code, although it's unclear what the consequences of that issue are in the various versions of Firefox.
You need to log in before you can comment on or make changes to this bug.