If the process from a previous test still exists, so will its unclosed
file descriptors and the associated storage blocks. Check ps in an
adb shell.
An interesting hack might be to register a file change notifier on
some part of yourself and finish() if it triggers... (indicating a new
version)
You didn't say what OS version you have or how big your app is. I'm
guessing you have a G1 and a HUGE app.
I've never seen this happen myself but my apps are small and I'm
currently testing on 2.2 devices.
-John Coryat
--
You received this message because you are subscribed to the Google
On linux, if you delete a file which soneone else has an open file
handle to, it doesn't actually go away until all handles are closed
(you just can't find it by name to open new ones). I'm guessing that
when you install a new version during a development session the old
version isn't completely
Hmmm.. yeah, makes sense. I wonder if my app is somehow not releasing
something.. somewhere.
The only thing that I'm doing that may be slightly left of center is
loading a native lib. AFAIK there is no way to unload a native
lib. Can't see a reason why this would cause a file handle to be left
4 matches
Mail list logo
