|
|
 Originally Posted by biggamer3
What's going on?
I even have ZERO cards sometimes and it gives me this error.
What's the deal, its been like this for a month now
two more suggestions (actually three):
1) this first one I think you have essentially done already: reboot the phone periodically - I do this by first holding down the power button until the Palm logo appears. This starts a shutdown of Linux. Once the Palm logo dissapears and the screen is dark, then the phone is off. Next you press and hold the power button again until the Palm logo appears again. Now your phone is booting up. Once your background image shows, you know that the phone has been fully rebooted. While you've essentially done these steps already, consider them a "prerequisite" or initial step to clear out problems so that you can "observe" behavior in the steps that I list next:
2) If you know how to put your pre in dev mode (what some here call "rooting"), or you have rooted your Pre and can ssh into it, then your next step will be to run a program like "top", then press the capital M key while top is running. The top program shows a list of processes and the screen periodically refreshes every few seconds. Pressing the M key causes top to show a list of processes sorted by memory usage. Observe how much memory some of your top processes are using.
3) Your next step is to experiment a bit. My assertion is that the Pre's memory management in its JVM is not the best (yet). Before opening any cards after the reboot, make a note of how much memory is free. With a freshly rebooted Pre, you should be able to open about 12 cards before getting the "too many cards" message. Next close out all the cards and note that the amount of free memory is less than after the fresh reboot. (Normally this would be OK for the memory to not free up immediately. The thinking is that if a running app previously needed memory, it might need it again so keeping it reserved for a bit would not necessarily be a bad thing. The trouble is that the memory should be freed shortly after closing an app, but the JVM periodically reschedules when it will reclaim the memory. I've never been patient enough to wait long enough to observe if this actually does happen. My suspicion/observation is that if you limit yourself to only opening 3 or 4 cards that the problem you have been seeing does not manifest itself. (You can occasionally go up to 5 or 6 cards, but if you start seeing slowdowns, you are pushing it too much.) I don't believe the JVM recovers well from this. I could be wrong - I'm just telling you what works for me.
This appears to be an area that Palm has worked on in WebOS 1.2. I didn't get 1.2 so I'm just going by what others have said. They say that things like the sluggishness in the phone app have improved. That sluggishness is another manifestation of this same problem. I predicted that this would be an area that Palm had to be working on in 1.2 and it appears from what I've read that this is indeed the case. My advice is to limit the number of cards you have open in the meantime, and hope for better behaviour once WebOS 1.2 is released.
PS: You don't have to do step 2 if you are not a "rooting" type of person. You can just do steps 1 and 3. Step 2 is only if you want to better understand the problem so that you can fine tune the steps you take to avoid it.
|
|
|
Posting Permissions
