Om de ûnderfining foar jo te ferbetterjen is tydlik de funksjonaliteit dan dizze website troch ûnderhâldswurk beheind. Wannear in artikel jo probleem net oplost en jo in fraach stelle wolle, kin ús stipemienskip jo helpe yn @FirefoxSupport op Twitter en /r/firefox op Reddit.

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.

How do I stop automatic generation of GC and CC logs?

  • 2 antwurd
  • 11 hawwe dit probleem
  • 10 werjeftes
  • Lêste antwurd fan Serrana

more options

I have the latest version of Firefox on my Nexus 7 2013 tablet, and for the past few months I have noticed a folder (memory-reports) appear in my download folder. This is full of GC and CC log files, which when I first found it, was over 5Gb in size, causing my tablet to report it was out of storage space. After deletion, the folder reappeared, filling once again with log files.

Is it possible to stop the automatic generation of these reports, as currently, I need to delete this folder every few days in order to create enough room on my tablet.

Many thanks.

I have the latest version of Firefox on my Nexus 7 2013 tablet, and for the past few months I have noticed a folder (memory-reports) appear in my download folder. This is full of GC and CC log files, which when I first found it, was over 5Gb in size, causing my tablet to report it was out of storage space. After deletion, the folder reappeared, filling once again with log files. Is it possible to stop the automatic generation of these reports, as currently, I need to delete this folder every few days in order to create enough room on my tablet. Many thanks.

Alle antwurden (2)

more options

In about:config you should check that memory.dump_reports_on_oom is set to false.

more options

kbrosnan said

In about:config you should check that memory.dump_reports_on_oom is set to false.

I had a look, and yes, it was already set to false. Thanks for the suggestion though :-)