Closed Bug 1235979 Opened 10 years ago Closed 10 years ago

3d transforms trigger many lines of terminal-spam like "depth 0x7fb2783f9d30 0.000000"

Categories

(Core :: Layout, defect)

defect
Not set
normal

Tracking

()

RESOLVED FIXED
mozilla46
Tracking Status
firefox43 --- unaffected
firefox44 --- unaffected
firefox45 --- unaffected
firefox46 --- fixed

People

(Reporter: dholbert, Assigned: RyanVM)

References

Details

(Keywords: regression)

STR: 1. Start Firefox (opt or debug, doesn't matter) from the terminal. 2. Visit vulturiceye.com 3. Hover some piece of the page, and watch your terminal. ACTUAL RESULTS: Many lines like the following: depth 0x7fb2834e4020 0.000000 depth 0x7fb283428530 0.000000 depth 0x7fb2834e5020 0.000000 depth 0x7fb283428530 0.000000 depth 0x7fb2834e5020 0.000000 depth 0x7fb283428530 0.000000 depth 0x7fb2834e5020 0.000000 EXPECTED RESULTS: No such terminal-spam. I'm pretty sure this is coming from this line, added in bug 1226904's patch: > 1959 printf("depth %p %f\n", transform, transform->GetHitDepthAtPoint(aBuilder, point)); http://hg.mozilla.org/mozilla-central/rev/f950b7a04741#l1.91 Thinker, do we need this line, or can we get rid of it? (I'm guessing it was just some debug logging that got left in by accident?)
Flags: needinfo?(tlee)
Blocks: 1236228
Right! I would remove it.
Flags: needinfo?(tlee)
No longer blocks: 1236228
Landing the one-liner with rs=thinker. Calling Fx45 affected since bug 1226904 is almost certain to be uplifted there at some point as well. https://hg.mozilla.org/integration/mozilla-inbound/rev/d3866546b914
Assignee: nobody → ryanvm
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla46
I was going to uplift this to aurora, but it looks like the patch for bug 1226904 that got uplifted to aurora didn't include the printf line to begin with.
Blocks: 1240783
This along with the change that caused this regression were backed out from Firefox 45. https://hg.mozilla.org/releases/mozilla-aurora/rev/64ec448f156d
You need to log in before you can comment on or make changes to this bug.