1186113 - Disable mozSettings debugging by default

Status: RESOLVED DUPLICATE of bug 1119727

(Core :: DOM: Core & HTML, defect)

Description

[Eric Rahm [:erahm]]

+++ This bug was initially created as a clone of Bug #1106896 +++

Bug 1106896 added both verbose and debug logging to mozSettings and turned on debug logging by default. This is rather spammy during test runs, it might make sense to disable debug output it by default.

In particularly we're seeing messages like:
> -*- SettingsRequestManager: Settings queue head blocked at {d642cf55-bd1f-4913-b76c-94514eafa549} for 94.187 secs, Settings API may be soft lockup. Lock from: SettingsServiceLock@jar:file:///system/b2g/omni.ja!/components/SettingsService.js:80:17

Hundreds of times during emulator runs.

Comment 1

[Eric Rahm [:erahm]]

Attachment: Disable mozSettings deubg logging by default

Comment 2

[:gerard-majax]

Comment on attachment 8636700 [details] [diff] [review]
Disable mozSettings deubg logging by default

This debug should not be that spammy, it's the default on device. The issue you point at is already filled, as documented in bug 1119727 comment 9. The fix should not be hard, just making the value configurable so that tests can set a higher threshold.

Comment 3

[:gerard-majax]

Marking as a dupe since the real issue here is just the threshold value which is too low for slow emulator tests.