We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

Questo sito potrebbe offrire funzionalità limitate durante le operazioni di manutenzione per migliorare l'esperienza utente. Se un articolo non risolve il tuo problema e vuoi richiedere supporto, la nostra comunità di supporto è pronta ad aiutarti tramite @FirefoxSupport su Twitter e /r/firefox su Reddit.

Cerca nel supporto

Attenzione alle mail truffa. Mozilla non chiederà mai di chiamare o mandare messaggi a un numero di telefono o di inviare dati personali. Segnalare qualsiasi attività sospetta utilizzando l'opzione “Segnala abuso”.

Ulteriori informazioni

Questa discussione è archiviata. Inserire una nuova richiesta se occorre aiuto.

feedback, why are crash symbols showing a timestamp of 2010 so it appear OUTDATED?!

  • 8 risposte
  • 1 ha questo problema
  • 1 visualizzazione
  • Ultima risposta di cor-el

more options

The crash symbols are showing a timestamp of 2010 so it appears they are NOT being complied FRESHLY... this should be looked into...

for example... the crash symbols for Firefox 67.0.4 https://ftp.mozilla.org/pub/firefox/candidates/67.0.4-candidates/build1/win64/en-US/firefox-67.0.4.crashreporter-symbols.zip

01/01/2010 @ midnight...


this is feedback and should be looked into...

The crash symbols are showing a timestamp of 2010 so it appears they are NOT being complied FRESHLY... this should be looked into... for example... the crash symbols for Firefox 67.0.4 https://ftp.mozilla.org/pub/firefox/candidates/67.0.4-candidates/build1/win64/en-US/firefox-67.0.4.crashreporter-symbols.zip 01/01/2010 @ midnight... this is feedback and should be looked into...

Soluzione scelta

In the case of the user agent this is a decision to anonymize the user agent.

There is more to come:

Leggere questa risposta nel contesto 👍 0

Tutte le risposte (8)

more options

Is this causing a problem?

I don't know which department would be able to respond to this feedback. Perhaps release management??

more options

Your Firefox user agent has the same 20100101 time stamp: Gecko/20100101

more options

jscher2000 said

Is this causing a problem? I don't know which department would be able to respond to this feedback. Perhaps release management??

causing a problem? not that I know of yet.... I have keeped my copy of crash reporter symbols up to date... but the time stamps are out of date..

more options

cor-el said

Your Firefox user agent has the same 20100101 time stamp: Gecko/20100101

I see what you mean... I looked up mine in About:config... I wonder why this is the case...

more options

Soluzione scelta

In the case of the user agent this is a decision to anonymize the user agent.

There is more to come:

more options

I don't see the point of doing that... Firefox Devs need to know what version of Firefox a crash was used on plus for other reasons too probably...

more options

Melchior (aka Joseph) said

Firefox Devs need to know what version of Firefox a crash was used on plus for other reasons too probably...

If your Firefox crashed this year and you submitted a crash report, you can use the "View" button for a report on the about:crashes page to see what information the crash reporter is able to gather. It's definitely not limited to what is in your user agent string.

more options

The Telemetry environment shows all data that is included in the crash report in JSON format. This includes processor (CPU) and OS information and display (graphics card and monitor).