Closed Bug 1245825 Opened 8 years ago Closed 8 years ago

Spamming prints from AlarmService

Categories

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

Product:
Core
Component:
DOM: Core & HTML
Version:
47 Branch
Type:
defect
Priority:
Not set
Severity:
minor

Tracking

()

Status:
RESOLVED DUPLICATE of bug 1240330

People

(Reporter: jujjyl, Unassigned)

Details

(Keywords: regression) 

Recently, I have started getting a lot of spammy prints from AlarmService in the OS X Terminal window when starting up Firefox Nightly from command line. These look like developer's internal debug prints:

AlarmService: remove(-6, undefined)
AlarmService: _removeAlarmFromDb()
AlarmService: Callback after removing alarm from database.
AlarmService: Current alarm: null
AlarmService: Alarm queue: []
AlarmService: observe(): profile-change-teardown
AlarmService: uninit()

It would be better to put these behind some kind of debugging flag so that they don't create spam for everyone.

(Not sure what would be the correct category for this report, so just marking down as Firefox/General to start with)
OS: Unspecified → Mac OS X
Hardware: Unspecified → x86
Version: 43 Branch → 47 Branch
Severity: normal → minor
This should use Log.jsm or Console.jsm with a debug level pref and so on. Tim or Fabrice, can you fix this?
Component: General → DOM
Flags: needinfo?(tihuang)
Flags: needinfo?(fabrice)
Keywords: regression
OS: Mac OS X → All
Product: Firefox → Core
Hardware: x86 → All
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → DUPLICATE
Flags: needinfo?(tihuang)
I'm fixing that in bug 1240330
Flags: needinfo?(fabrice)
Component: DOM → DOM: Core & HTML
You need to log in before you can comment on or make changes to this bug.