OS2008 Open-File Dialog Screwed Up
 

A few users reported that some of my programs show 100+MB virtual memory footprints in "top". While "top" is known as a fairly unreliable tool, 100+MB VSZ still looked unnatural. So, I investigated and here is what I found:

It is Maemo File-Open dialog. You can run pretty much ANY program using it, run "top" in a separate ssh. Then invoke that dialog and see program's virtual memory size grow to 100+MB. You don't need to actually open a file, just click Cancel - the dialog will disappear but the VSZ will stay above 100MB.

Whoever feels like filing a bug with Nokia, please do it. I am tired and generally can't bring myself to doing it.

Re: OS2008 Open-File Dialog Screwed Up
 

Try using the gtk one, should be working. Not very finger-friendly though :)

Re: OS2008 Open-File Dialog Screwed Up
 

a discussion was raised in the mailing list about this topic some time ago: http://lists.maemo.org/pipermail//ma...ry/014513.html

Re: OS2008 Open-File Dialog Screwed Up
 

No answers to his question though :(

Re: OS2008 Open-File Dialog Screwed Up
 

The answer is: it's not real memory so you don't should worry about it.

What is shown if you run this?
awk '/Private_Dirty/{sum+=$2}END{print sum "kB"}' /proc/(here PID of your app)/smaps

It's the memory what should worry you.

Re: OS2008 Open-File Dialog Screwed Up
 

I know that it is not the real footprint. But still, it is not normal for the file open dialog to request that much memory, even potentially.

Re: OS2008 Open-File Dialog Screwed Up
 

My guess is that the file dialog uses that much or less memory at one time to index the subdirectories... Probably with several threads.

Re: OS2008 Open-File Dialog Screwed Up
 

well im not too sure but mine spikes whene it sees local drives and bluetooth drives sometimes i wish i had a reset on this thing...kinda like pdas...