
Originally Posted by
rjax
Gary, as usual, nice job with the updates, particularly the new tab switcher.
I was using my Droid today to do a good bit of browsing (which for me on xScope means that I do a lot of opening up links to the background from one page until six tabs are open, then reading and closing all but one tab, then repeating the cycle), and I noticed a few issues that may or may not be tied together.
The first thing was my first force close experience (it only happened once) -- after probably 3 or 4 cycles of tab-opening, xScope froze in the middle of a web page -- I hit "wait" a couple times, but to no avail, and I was forced to force close.
I'm wondering if maybe there's just too much memory that ends up being used after a couple cycles because I've noticed strange behavior when I try to use the back button to close a tab (my preferred method). Basically, hitting back works great the first cycle, but after I open 5 new tabs, hitting back doesn't close the tab immediately, but instead takes me a page that was in one of the 5 tabs that I closed in the previous cycle. (You can also replicate this behavior by opening one tab, then closing it, doing that 5 times, then the sixth time you hit back, it takes you back the first new tab; the seventh time you hit back, you go back to the second new tab, etc.)
But probably the biggest problem is closing tabs after a cycle or two. I can't replicate at will, but every now and then, closing a tab closes all of xScope, even when there is more than one tab open. This has happened at least once for each method of tab-closing (back key, tapping on the tab currently in focus, and closing a tab from your new tab switcher).
The worst part is that when I start xScope back up after this happens, I'm back at my home page instead of your neat tab-restore feature kicking in. Also frustrating is that the history doesn't seem very reliable at all, to the point where most/all tabs I open don't appear in the history, even though sites I visited before opening the tabs show up in the history.
I've tried to make sure I have plenty of memory available when I open xScope (killing everything but a couple background apps that I prefer to be on all the time leaves me with 80-90M of memory before starting xScope), but I'm still consistently getting the xScope memory low notification, even after I've hit the "ignore future notifications" choice. Also, I was rather surprised to see to that xScope actually used more battery than the display during all this time.
Anyway, hopefully this will give you some direction on further optimization. I admit to being curious how the memory usage/battery performance would change without the embedded task manager/memory monitor/file manager...