Ky sajt do të funksionojë me kufizime, teksa bëjmë mirëmbajtjen e tij për të përmirësuar punën tuaj. Nëse një artikull nuk e zgjidh problemin tuaj dhe dëshironi të bëni një pyetje, kemi bashkësinë tonë të asistencës, e gatshme për t’ju ndihmuar, te @FirefoxSupport në Twitter dhe/r/firefox në Reddit.

Kërkoni te Asistenca

Shmangni karremëzime gjoja asistence. S’do t’ju kërkojmë kurrë të bëni një thirrje apo të dërgoni tekst te një numër telefoni, apo të na jepni të dhëna personale. Ju lutemi, raportoni veprimtari të dyshimtë duke përdorur mundësinë “Raportoni Abuzim”.

Mësoni Më Tepër

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

  • 2 përgjigje
  • 11 e kanë hasur këtë problem
  • 1 parje
  • Përgjigjja më e re nga 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.

Krejt Përgjigjet (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 :-)