----- Original message ----- > kate.alh...@nokia.com<mailto:kate.alh...@nokia.com> wrote: > > I don't know hat mappero (ex maemo mapper) does internaly but least, > it > > can eat all cpu power when doing "processing maps" so that only way > out > > is remove battery from device. > > I've been told that this happens when downloading large amounts of map > tiles, so > it has nothing to do with the map widget itself. That one is based on > clutter, > and seems to be quite efficient.
Situation is when lot of map tiles are loaded. I dont't know what internaly happens. Some memory leak ? For application performance and cpu usage also time needed for tile pre-processing need to be counted. Does it some scaling for tiles after loading them ? Finally time used for scaling tiles is one key issues. Do we scale them or download every size. How much cpu power is used for scaling or do we leave it all for GPU ? For mappero case i don't know how much cpu is used for actual scaling and how much by exhausting virtual memory ? > (off topic: if you can find some way to reproduce it reliably, please > file a bug > -- although if you really need to take out the battery, that cannot be a > bug in > the application itself) I think, without any actual debug or analysis that it consumes all virtual memory and there won't be any memory for system UI even kill application when everything is swapped out. Kate > > Ciao, > Alberto > > -- > http://blog.mardy.it <-- geek in un lingua international! >
_______________________________________________ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
