Important Notice: We're experiencing email notification issues. If you've posted a question in the community forums recently, please check your profile manually for responses while we're working to fix this.

On Monday the 3rd of March, around 5pm UTC (9am PT) users may experience a brief period of downtime while one of our underlying services is under maintenance.

Cari Bantuan

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Pelajari Lebih Lanjut

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

  • 2 balas
  • 11 memiliki masalah ini
  • 1 kunjungan
  • Balasan terakhir oleh 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.

Semua Balasan (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 :-)