Poll: Which apps have known memory leaks and/or are causing your WebOS device to slow down?
Daniel Rodriguez
We know Palm is working on speed and hopefully they can get this rumored speed increase out the door by the Pixi's launch but, we don't know if Palm is completely aware that some apps have memory leaks that slow down the device. When I first turn on my device it runs smooth. Even with all the complaints of lag when it is first turned on it runs really fast throughout every app but, as the day goes on it slows down a great deal. So we want to hear from you about which apps have memory leaks or are causing your phone to slow down.
Vote which apps are having problems after the break!
You can select up to 3 boxes. Try to be as honest as possible and let us know which apps are having lag issues or memory leaks. If there is an app not listed in the pole or one of the homebrew apps feel free to let us know in comments which apps you are having problems with.
Reader Comments (10)
I had an issue with the ActiveCard (beta) homebrew app. Keep giving me a too many cards open error when I had it open.
Web browser! I really think it is the browser. That is where I have most my issues after I use the browser. And almost all homebrew apps for some reason. (maybe it is quick install or filecoaster)
CLASSIC!!! If you definitely want to make your Pre crawl, then use Classic!
This could be the most scientific poll ever...
Seriously, it takes a very controlled test to say an app has memory leak.
PreWare turned my system into a slug. Took it off and all was well.
I was using my calendar earlier today, and it locked up momentarily.
Come on, 1.3.1!
I think the poster was attempting to just find out what apps are slowing your Pre..... dunno if there needs to be any scientific analysis for that
i had an issue with one of the concert apps killing my battery. uninstalled it and it was solved immediately
Evernote, much to my dismay. I load that and everything else slows to a stop.
I can tell which apps use a lot of resources (web browser, Pandora), but that has nothing to do with memory leaks.
Besides, JavaScript uses managed memory. If there were a memory leak, it would be in the Mojo framework or Pre's rendering engine, not the apps themselves. For example, there could be a memory leak in the way that the Pre opens apps, so no matter which apps you open, each one leaks a little bit. There's no way to tell without serious testing.