Created attachment 664190 [details] [diff] [review] patch
Attachment #664190 - Flags: review?(ted.mielczarek)
Attachment #664190 - Flags: review?(ted.mielczarek) → review+
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla18
Comment on attachment 664190 [details] [diff] [review] patch [Approval Request Comment] Bug caused by (feature/regressing bug #): me not thinking we'd need symbols when I wrote this configure goop User impact if declined: no user impact, but developers will continue to have useless stacks in crash-stats Testing completed (on m-c, etc.): on trunk for a week, useful stacks have let us fix several bugs Risk to taking this patch (and alternatives if risky): no risks I can identify String or UUID changes made by this patch: none
Leaving this approval nom, we can make sure it lands post-merge on Oct 8th and gets into the first 17.0 beta
Lukas, I was suggesting that we get this into 16 and 17.
Comment on attachment 664190 [details] [diff] [review] patch Beta is representative enough that we should be able to make bugs actionable there (17), and we've already gone to build on 16 so it's unfortunately too late - fortunately this isn't too critical.
Setting tracking for 16, if there was a chemspill we would consider this for a ride-along.
status-firefox16: --- → affected
status-firefox17: --- → affected
status-firefox18: --- → fixed
tracking-firefox16: --- → +
tracking-firefox17: --- → +
status-firefox17: affected → fixed
Flagging as [qa-] since I don't believe this to be something QA needs to verify.
You need to log in before you can comment on or make changes to this bug.