Closed Bug 1178155 Opened 9 years ago Closed 9 years ago

Unconditional printf landed in SetInRuleProcessorCache

Categories

(Core :: CSS Parsing and Computation, defect)

Product:
Core
Component:
CSS Parsing and Computation
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED WORKSFORME

People

(Reporter: MattN, Unassigned)

References

Details

I get this output at startup in a new profile:
0x11c760f60 SetInRuleProcessorCache 1
0x11e62c5f0 SetInRuleProcessorCache 1
0x11fb1d190 SetInRuleProcessorCache 1
0x122658ef0 SetInRuleProcessorCache 1
0x122658f60 SetInRuleProcessorCache 1
0x123ee66a0 SetInRuleProcessorCache 1
0x123ee68d0 SetInRuleProcessorCache 1
0x123ee6da0 SetInRuleProcessorCache 1
0x11b235b30 SetInRuleProcessorCache 1
0x11b235ba0 SetInRuleProcessorCache 1
0x11b2d6a50 SetInRuleProcessorCache 1
0x11efc0b70 SetInRuleProcessorCache 1
0x11effee10 SetInRuleProcessorCache 1
0x11c760f60 SetInRuleProcessorCache 0
0x122658ef0 SetInRuleProcessorCache 0
0x123ee66a0 SetInRuleProcessorCache 0
0x11b235b30 SetInRuleProcessorCache 0

I assume this wasn't intentional but perhaps the idea was to convert it to a logging statement?
I forgot to remove it before landing but 77999.  I did remove it a couple of days ago, but it's still waiting to be merged to mozilla-central: https://hg.mozilla.org/integration/mozilla-inbound/rev/9798c03e3909
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.