![]() |
2009-11-09
, 16:59
|
Posts: 716 |
Thanked: 303 times |
Joined on Sep 2009
@ Sheffield, UK
|
#2
|
![]() |
2009-11-09
, 17:00
|
Posts: 21 |
Thanked: 13 times |
Joined on Oct 2009
|
#3
|
Having had the privilege to use the Summit N900 for almost a month now, I'd like to discuss how to handle "Out of memory" errors and UI freezes that sometimes occur on the N900. (extras-testing enabled and apps in use).
From time to time, the device gives "out of memory errors". Sometimes the message can be ignored, other times the battery has to be removed. I have been assuming apps from extras-testing is the primary cause. How to optimally troubleshoot this?
The crash reporter is useful for crashes, but not for UI freezes. How does one trace the origins of temporary (say, 5-10 sec) or permanent UI freezes (where a reboot is necessary)? How to find out whether this is simply a result of memory shortage, that would/should not happen without apps from extras-testing? UI freezes are also hard to bug report, like this one. And what to do when cpu usage generally is high without any obvious reason, or when the OS gets sluggish?
The Following User Says Thank You to vitb For This Useful Post: | ||
![]() |
2009-11-10
, 07:27
|
Posts: 133 |
Thanked: 23 times |
Joined on Oct 2009
|
#4
|
The Following User Says Thank You to bemymonkey For This Useful Post: | ||
![]() |
2009-11-10
, 07:46
|
Posts: 103 |
Thanked: 157 times |
Joined on Feb 2007
@ Jyväskylä, Finland
|
#5
|
The Following User Says Thank You to mve For This Useful Post: | ||
![]() |
2009-11-10
, 07:55
|
Posts: 133 |
Thanked: 23 times |
Joined on Oct 2009
|
#6
|
![]() |
2009-11-10
, 08:35
|
Posts: 268 |
Thanked: 304 times |
Joined on Oct 2009
@ Orlando, USA
|
#7
|
![]() |
2009-11-10
, 08:42
|
Posts: 268 |
Thanked: 304 times |
Joined on Oct 2009
@ Orlando, USA
|
#8
|
Cool. Have you gotten the N900 to run out of memory by just opening a _lot_ of applications? I'd love to know how many browsers you can open side by side without slowing down the system before everything bogs down or the phone just crashes...
![]() |
2009-11-10
, 08:59
|
Posts: 133 |
Thanked: 23 times |
Joined on Oct 2009
|
#9
|
![]() |
2009-11-10
, 09:41
|
|
Moderator |
Posts: 199 |
Thanked: 264 times |
Joined on May 2009
@ turku, finland
|
#10
|
The 'Out of Memory' message is due to the rootfs filling up. This can happen if you are installing applications from extras-testing that take large amounts of space and aren't optified.
the root partition can also fill up if a bunch of apps are quickly installed and uninstalled. there is a BZ tracking that issue already. Rebooting seems to be the workaround at the moment.
I have experienced OS sluggishness a couple of times in the past 4 weeks. I think this happens because of apps leaking memory and if I haven't rebooted in a while.
I wonder why apps like modest, camera-ui, browserd each use about 20mb of memory even when they are not open.
Anywya, Xorg runs with a log file in /tmp/Xorg.0.log. It may provide helpful information when reporting bugs related to UI slowdown.
From time to time, the device gives "out of memory errors". Sometimes the message can be ignored, other times the battery has to be removed. I have been assuming apps from extras-testing is the primary cause. How to optimally troubleshoot this?
The crash reporter is useful for crashes, but not for UI freezes. How does one trace the origins of temporary (say, 5-10 sec) or permanent UI freezes (where a reboot is necessary)? How to find out whether this is simply a result of memory shortage, that would/should not happen without apps from extras-testing? UI freezes are also hard to bug report, like this one. And what to do when cpu usage generally is high without any obvious reason, or when the OS gets sluggish?