Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

Sykje yn Support

Mij stipescams. Wy sille jo nea freegje in telefoannûmer te beljen, der in sms nei ta te stjoeren of persoanlike gegevens te dielen. Meld fertochte aktiviteit mei de opsje ‘Misbrûk melde’.

Mear ynfo

Dizze konversaasje is argivearre. Stel in nije fraach as jo help nedich hawwe.

What causes Error Console to report a TelemetryStopwatch error every few minutes?

  • 2 antwurd
  • 1 hat dit probleem
  • 2 werjeftes
  • Lêste antwurd fan GilDawson

more options

While debugging my JavaScript code, I find the Error Console very useful. Besides the errors in my code, it also shows error messages about other peoples' code for sites that I have open. This is a little annoying, because I have to click "Clear" each time or else scroll down to see my error messages.

To simplify matters, I closed all tabs and windows except my own window (without tabs) where I'm testing my JavaScript program. All the other error messages disappeared -- except one. This lone leftover message appears every few minutes in PINK (I guess that means it's serious) even when my program's window is the only one open, without any tabs:

Timestamp: 12/14/12 11:47:39 AM Error: TelemetryStopwatch: key "FX_SESSION_RESTORE_COLLECT_DATA_MS" was already initialized Source File: resource://gre/modules/TelemetryStopwatch.jsm Line: 53

I clicked on the Source File (it's blue and underlined in the original) and up popped a source listing of some file from inside the Firefox.app package. Lines 52 and 53 read as follows:

     Cu.reportError("TelemetryStopwatch: key \"" +
                    aHistogram + "\" was already initialized");

Any idea what this is about?

--Gil

While debugging my JavaScript code, I find the Error Console very useful. Besides the errors in my code, it also shows error messages about other peoples' code for sites that I have open. This is a little annoying, because I have to click "Clear" each time or else scroll down to see my error messages. To simplify matters, I closed all tabs and windows except my own window (without tabs) where I'm testing my JavaScript program. All the other error messages disappeared -- except one. This lone leftover message appears every few minutes in PINK (I guess that means it's serious) even when my program's window is the only one open, without any tabs: Timestamp: 12/14/12 11:47:39 AM Error: TelemetryStopwatch: key "FX_SESSION_RESTORE_COLLECT_DATA_MS" was already initialized Source File: resource://gre/modules/TelemetryStopwatch.jsm Line: 53 I clicked on the Source File (it's blue and underlined in the original) and up popped a source listing of some file from inside the Firefox.app package. Lines 52 and 53 read as follows: Cu.reportError("TelemetryStopwatch: key \"" + aHistogram + "\" was already initialized"); Any idea what this is about? --Gil

Bewurke troch GilDawson op

Keazen oplossing

hello gil, usually after a fresh install firefox asks you to help by submitting performance data to mozilla. this is internally dubbed "telemetry", so the error you're seeing is likely linked to this functionality.

according to bug #732874 this will be fixed in the next version of firefox. in case you want to, you can also disable the gathering & submission of performance data in preferences > advanced > general for the moment...

Dit antwurd yn kontekst lêze 👍 0

Alle antwurden (2)

more options

Keazen oplossing

hello gil, usually after a fresh install firefox asks you to help by submitting performance data to mozilla. this is internally dubbed "telemetry", so the error you're seeing is likely linked to this functionality.

according to bug #732874 this will be fixed in the next version of firefox. in case you want to, you can also disable the gathering & submission of performance data in preferences > advanced > general for the moment...

more options

Thanks, madperson, for an excellent reply. It seems to be working!

--Gil