1162270 - get_about_memory.py leaves large files in /data/local/tmp/memory-reports/

Status: RESOLVED WORKSFORME

(Firefox OS Graveyard :: General, defect)

Description

[Myk Melez [:myk] [@mykmelez]]

get_about_memory.py leaves large files in /data/local/tmp/memory-reports/.

After running the script a couple dozen times, I run out of space on my Flame's 2GB /data partition, which can cause a variety of problems.  I initially noticed it in an app that was failing due to a "quota exceeded" exception during an IndexedDB transaction.

Since the script downloads those files to your desktop, and they're presumably only useful for analysis there, it should delete them from the device after downloading them.

Comment 1

[Eric Rahm [:erahm]]

(In reply to Myk Melez [:myk] [@mykmelez] from comment #0)
> get_about_memory.py leaves large files in /data/local/tmp/memory-reports/.
> 
> After running the script a couple dozen times, I run out of space on my
> Flame's 2GB /data partition, which can cause a variety of problems.  I
> initially noticed it in an app that was failing due to a "quota exceeded"
> exception during an IndexedDB transaction.
> 
> Since the script downloads those files to your desktop, and they're
> presumably only useful for analysis there, it should delete them from the
> device after downloading them.

Myk, which FxOS version were you testing with? It's possible newer versions of the script aren't properly cleaning up non-unified reports that were present in older versions of FxOS.

Comment 2

[Myk Melez [:myk] [@mykmelez]]

I was testing on 2.0, but I just tried again and can't reproduce.  Strange.  I then updated my b2g clone, which applied some changes to get_about_memory.py, and tried again.  It worked fine that time too.  Then I tried it on a Flame running 2.1, and everything was as expected there: the files are deleted after they're downloaded.

So I guess this is worksforme, although it wasn't yesterday.  Unsure why, I don't have those files anymore, as I deleted them to free up the space.  So I'll resolve this and reopen if I see the problem again.