Related
So...I am running Fresh 1.1, and I flashed Madaco's new kernel...then I enabled compcache.
Ever since flashing the new kernel, my Taskiller widget (which now shows how many MB's of memory you have available) will start at about 94mb when I power on my phone. Throughout the day, as I use taskiller to close programs, the memory doesn't go back to 94mb, but slowly goes down. First it'll go to 90mb...than 88...than 82....than 66...and all the way down to 54. It decreases each time I use the taskiller saying that my maximum freed up memory is only at 54mb, when in the morning it started at 94mb.
Can anyone help me with this? or help me figure out why it might be doing this? Sorry if the description of what's happening is kind of confusing, but I don't know how to explain it any clearer.
Thanks for any help given!
You really shouldn't be using TasKiller. Find out why here: http://geekfor.me/faq/you-shouldnt-be-using-a-task-killer-with-android/
Uninstall TasKiller and you should be fine.
I use it cause the apps build up and kill my battery.
I stopped using any task managers for 2 weeks and my phone never really got any faster it actually was much worse when using the keyboard so I tried using them again and it's not as laggy anymore I don't really know how true that is I believe Fresh but it didn't help me
I've read about not using taskiller elsewhere, but I swear it makes a difference. Whenever I am experiencing lag, I run it, and boom...the lag is gone. It's not just my imagination either.
But back to the question: Why the heck would the available memory be going down each time I use taskiller?
I get the same thing and I have always wondered this also I will start out with a good amount of memory and later on in the day I might be able to get half of the memory I started with freed up
Could some kind soul please tell me what the following processes do?
sensorserver_ya
drexe
rild
events/0
mmcqd
pvr_workqueue
Thank you!
I saw your posts in the battery life thread and dig some digging after looking at my SystemMonitor results. These are pretty much all showing up in my System Processes list as well. Here's what I've found so far:
sensorserver_ya - Tied to the use of the accelerometer. This was showing constant CPU usage while ShootMe was running because it actives by shaking. As soon as I stopped ShootMe, this disappeared.
drexe - This one was showing almost constant 1% CPU usage. According to this thread, drexe and another process are both for some Samsung software called NPS(New PC Studio,) which I have never used and don't plan on using. I took the advice of the post and disabled them using adb. I'll report back results after a day or so.
Let me know if you've found out anything about the rest. Maybe bumping this thread up will get some more eyes on it
Gix0r said:
I saw your posts in the battery life thread and dig some digging after looking at my SystemMonitor results. These are pretty much all showing up in my System Processes list as well. Here's what I've found so far:
sensorserver_ya - Tied to the use of the accelerometer. This was showing constant CPU usage while ShootMe was running because it actives by shaking. As soon as I stopped ShootMe, this disappeared.
drexe - This one was showing almost constant 1% CPU usage. According to this thread, drexe and another process are both for some Samsung software called NPS(New PC Studio,) which I have never used and don't plan on using. I took the advice of the post and disabled them using adb. I'll report back results after a day or so.
Let me know if you've found out anything about the rest. Maybe bumping this thread up will get some more eyes on it
Click to expand...
Click to collapse
Hi Gix0r,
Sorry for the late reply; I have not been spending much time in the forums these days.
Good job with the "digging" to find the purpose of the system tasks. What was your result from disabling drexe?
Thanks,
Bruce
Safely Dis-ablable System Processes
Although it applies to an earlier model phone, here is another link that underscores your last comment and has other ideas:
http://einartysen.se/tweak-your-android/
sensorserver_ya also works with GPS... Had this running while running the gps test thing.
I'd like to know if anyone is having the same lag problems as I am getting from time to time..
The lag happens for no reason and comes at different times while doing different things.
I downloaded Watchtower from the Android Market to monitor what was happening. When the phone is running fast the /INIT process is showing as 0%..as soon as the lag starts to happen I check Watchtower again and the /INIT process is at anywhere from 70% to 100% CPU usage.
I dont use an app killer but I donwloaded one to try and see if it would correct the problem, it doesn't. The only way to solve the lag is to Restart the phone, then its fine for the rest of the day, sometimes two days but it always comes back.
I sold my SGS because of the lag issue and now it seems I have it with the DHD..
I did google this and I found that it maybe something to do with android itself..looks like /INIT is an android process..
If you notice your DHD lagging then download Watchtower and I'd bet you will see the /INIT process killing your phone..
------------------------------------------------------------------------------------------------------------------------------------
EDIT - A fix has been found to stop the /Init process lagging the phone.
On your phone go to..
Menu/settings/applications/development/now turn on Usb debugging..
This seems to keep the / init process at 0% CPU usage, it also works when the /INIT problem starts, turning USB debugging on will make the /INIT process drop back to 0%, very nice to see.
Ive contacted the Dev to find out if he can tell us why this method has fixed the problem.
Still need an update from Htc but at least we can use our phones again..
There doesn't seem to be any negative effects from turning this option on, the only thing to note is turning it off to connect to your pc could bring the /init process back and lag your phone. You can download Android Manager from the market for free which will allow you to transfer data from your pc using Wi-Fi, using this app you can keep the USB Debugging on.
-------------------------------------------------------------------------------------------------------------------------------------
EDIT 2 - It looks like you can connect to the pc via USB cable with the debugging turned on without problems, the only difference is that it will try and install additional drivers...because of the debugging mode..
Im using windows 7 and the ABD driver wont install...you need to download Htc Sync on your pc which downloads the ABD driver !!
We should also watch the battery as this may actually increase battery life...
-------------------------------------------------------------------------------------------------------------------------------------
EDIT 3 - Not one single person has come back to me and said that the /INIT problem has returned after this fix...lets hope it stays that way.. 10/11/10
---------------------------------------------------------------------------------------------------------------------------------------------------
EDIT 4 - A lot of people including myself have found that this fix improves their battery life quite a bit.
-----------------------------------------------------------------------------
Last EDIT before thread is locked just for reference and to help people !!!
For people that have the com.htc.bgp process that loads the CPU it stays at 80-90% all the time, and i have autosync on, if you stop auto sync the process goes out....
So here is the final fix in the link below (post 7)
http://forum.xda-developers.com/showthread.php?t=659325
Thank you to everyone in this thread for there efforts...amazing response.
Thanks to all the XDA Community...Including the Devs and Mods
Thread Closed
nednapalm said:
I'm getting the problem.
No apps installed except the flash and maps update, oh and OS Monitor.
Have turned off "Fast Boot" and removed battery to reset, ok for now. Very scared to start installing more apps, nearly unusable when it is lagging
Click to expand...
Click to collapse
I also tried the "turn off fast boot and it was ok for 2 days, it came back this morning though..It is very worrying and yes, the phone is unusable until it is Restarted..Thanks for the reply.
sanju007 said:
LAG WHAT?
I hope not, the samsung galaxy s have lag issus and its very bad and i sold de sgs
And now the DHD gets also lag problems ?
Ik hope not, then i will not buy this phone
Maybe an good task killer wil help ?
More people have lag issus ?
Can you make a video ?
Click to expand...
Click to collapse
An app killer doesn't solve the problem and Im unsure how many people are having this problem, to my understanding its not many...that's why I started this thread to try and find out.
I wouldn't worry yet...
I will make a video when it happens again...it may take a few days to come back....but it always does...a video added to this thread would be most useful...just have to wait till it rears its ugly head again.
So it seems that /init is a core process regarding the initialisation of the Android system and userspace hence the fact it cannot be killed using OSMonitor. It is always the first process that runs on Linux systems after boot and acts as a parent process which itself initialises then processes needed to get the OS going.
Here is a description of the Android Init Process from elinux,
'init'
A key component of the Android bootup sequence is the program 'init', which is a specialized program for initializing elements of the Android system. Unlike other Linux systems (embedded or otherwise), Android uses its own initialization program. (Linux desktop systems have historically used some combination of /etc/inittab and sysV init levels - e.g. /etc/rc.d/init.d with symlinks in /etc/rc.d/rc.[2345]). Some embedded Linux systems use simplified forms of these -- such as the init program included in busybox, which processes a limited form of /etc/inittab, or a direct invocation of a shell script or small program to do fixed initialization steps.
The init program processes two files, executing the commands it finds in them, called 'init.rc' and 'init.<machine_name>.rc', where <machine_name> is the name of the hardware that Android is running on. (Usually, this is a code word. The name of the HTC1 hardware for the ADP1 is 'trout', and the name of the emulator is 'goldfish'.
the 'init.rc' file is intended to provide the generic initialization instructions, while the 'init.<machine_name>.rc' file is intended to provide the machine-specific initialization instructions.
The Bug
The /init bug has presented itself on numerous handsets including the HTC Desire, Nexus One and Droid X models. It seems to be specific to Android 2.2 and reports the same symptoms on all handsets. Primarily this is due the 99% CPU usage causing system slowdown and left unchecked, high battery usage. It is not specific to HTC Sense ROMs as it also presents itself on stock releases. The only solution so far is a reboot. Hard Reboots and altering system settings seem to have no effect on the reproduction of this bug.
I can only speculate to what is causing the issue and hopefully a Dev can shed some more light.
Logically it seems as though a 'rogue' process is triggering /init to resume its primary function in regards to checking filesystems and attempting to spawn other system process. Due to some form of miscommunication between the processes in question, /init continues to perform these post boot tasks in a constant loop.
Think of it like this, if you try perform tasks straight after boot, the phone is unresponsive while the SD is mounted/checked and all other processes are fired up. The /init process is responsible for these tasks. If it were to loop, you would experience the symptoms we are having.
I found this on Wikipedia:
After /init has spawned all of the processes specified, init goes dormant, and waits for one of three events to happen:- processes it started to end or die, a power failure signal[clarification needed], or a request via /sbin/telinit to further change the runlevel.
So our trigger should hopefully be narrowed down to these three events.
Regarding what I posted before, the connection between sync and the bug has proven itself to be a false one.
I've also noticed that sometimes the bug can be present, however there is little impact on the responsiveness of the OS. It can seem as though everything is ok yet the CPU load can be extremely high, resulting in poor battery performance.
Anyway, hopefully more people can contribute to this thread so we can build up a better picture of what is going on. I will also try and grab a Logcat and ask anyone else near their PC when it happens to do the same.
There is a thread here which has users complaining of the same problems, yet no solutions are presented. Hopefully we can make a bit more noise and get some definitive answers.
Regards.
Hey guys some great feedback here, as with my link on starting this thread the /INIT is an android 2.2 process, auto sync on/off doesn't solve the problem neither does a hard reset, taking the battery out ect...
The guy in the link says his method worked for him, can't say the same for myself, I have a feeling his problem will be back...but if it did fix it for him then thats great, just cant say the same for me
http://forum.xda-developers.com/show...3&postcount=42
I have gone 5 days without the problem coming back and then Oh no its back, sometimes it happens twice a day, all the above doesn't fix this problem im afraid from what I have experience anyway.
The /INIT process is only 132k, something so small causes the phone to be basically unusable....very frustrating.
The 1.32.405.6 update also doesn't solve this problem, I updated yesterday and 10 min later I had the dreaded /INIT problem...
The so called "turn off fast boot doesn't fix the problem either, I have had the /INIT lag problem with it switched on and off...
What I find to be the most strangest thing is that if this is indeed an android process which it most likely is then why doesn't every DHD phone have this lag from time to time???.....why only certain phones??..
I haven't had the problem since yesterday (around 12 midday), when it occurs again I will be posting a video as requested...
The mystery continues.......There is NO solution as yet that fixes this problem.
Thanks to Lynxboy, your posts give some good information.
I wonder if this has any relevance to the problem from a linux based PC..
It seems that /INIT uses the same Process ID - 1 (found from using watchtower)
http://www.yolinux.com/TUTORIALS/LinuxTutorialInitProcess.html
BigMango said:
You purchased it from ebay, but did you buy it from a shop or from an individual (second hand)?
If you got it from an ebay shop they should give you a receipt. If it was from an individual, he should give you his original receipt (that's when the warranty started).
Anyway, the phone has a 2 years warranty, so you are covered for the next 2 years minus 1 or 2 weeks. And the paypal transaction is a valid payment receipt (it can be verified directly with paypal); so even without the receipt from the first owner HTC should cover you since the phone can't be 2 years old.
Get in touch with HTC directly, they should replace it. But the tricky part is that the problem must happen when they check it out, for this reason I would also make a video of the problem the next time it happens and send it to them by email so they can keep it on file with your RMA.
Click to expand...
Click to collapse
Thanks for the advice, Im going to contact the seller, he had it on upgrade and shipped it to me the following day..he seemed a nice guy so It should be ok...Now its just a matter of waiting for MR INIT to show up haha....wonder if he wears a hoodie LOL
bimmerfox said:
I'm not wrong because I see it with my own eyes. Even my DHD had the same problems as described. After the update no more /INIT at 90% and it keeps running smooth now.
Try to keep your patience before quoting a person who is willing to help others.
Click to expand...
Click to collapse
What?? Why do you think I made this thread...to help myself and others...as we do at XDA....the update doesn't fix the problem....just because yours hasn't lagged since the update doesn't mean its fixed....I've gone 5 days with no lag and it came back...like yours probably will.
Ridiculous....
EDIT- You can't post a statement that the problem as been fixed when numerous people have done the update and still experienced the /INIT problem...how can it be fixed??...and since the update only came out yesterday you have no way of knowing this for sure... its way to early to say that.. Try reading through posts in the forum and gather some information next time.... the update was for the youtube fix, we're not even sure that HTC were aware of the problem at the time.
Hi guys,
Just finished work and have caught up with the thread since I last posted and wanted to clarify a few things. I would also ask any new readers to find my previous post which covers much of the nature of the /init process.
The problem is solely software based. The hardware is NOT at fault!
The /init process is the parent process of Android/Linux, hence the PID 1 in OS Monitor. Imagine it as the ignition system in your car. You need to turn the ignition to fire up the other systems and that technically is the role /init takes.
It is not a rogue process in itself. It cannot be killed or closed via a task manager.
The latest update was not a fix nor does it resolve the issue.
The bug IS a Froyo bug and affects numerous devices not just the DHD although it is not present in all Froyo ROMs.
It is possible the memory management is to blame however I have run many Froyo based ROMs from FRF55 and not experienced it before; they all use the same memory management.
The three triggers for /init to awaken after its boot tasks are completed are specified in my previous post. These are the most likely causes for our issue and are in my mind triggered by some rogue process interactions.
A logcat will only really be useful if it captures the event taking place. A logcat taken when the /init process has started will report back specifically that.
Just because you haven't experienced the bug in 2days doesn't mean you are bug free, nor is there a bad batch of phones as this would indicate a hardware issue.
Continuing this thought, it is possible if you are on a branded operator ROM you may be bug free.
The /init bug is extremely annoying.
Regards.
Yes off topic...
Im asking the mod to still keep this a sticky but to lock the thread as there is really nothing left to discuss and its just here for people that are still having the /init problem as a reference...
EDIT - Thread being locked soon so....
Agian thanks to all xda community !!
Is this stickie needed anymore? Has this been corrected by any software update?
I've had this problem since the day I got the phone (December 2010) and got it again today. Once I see the obvious lag of everything, I just restart.
If it can help...
I have noticed this phenomenon the first time just after installing 2 things in my DHD :
- creating the HTCSense account (and keeping it synchronized one a day)
- installing the HTC plugin for Picasa Web Albums in the Album application.
Maybe coïncidence, maybe not.
I have disabled all HTC Sense stuff I can see. It always happens when performing some action, like opening a new app. It seems to occur so randomly, it happened again the day after my last post, but has been fine since then.
Problems with calendar after removing cache and program data.
I had major problems with com.htc.bgp using up to about 90% of my processor from time to time. When I searched the forums I found this thread.
I tried what is stated in the top post and went ahead and cleared the calendar data and the gmaill data. This is all fine, I don't seem to get any more warnings about com.htc.bgp reaching the 90% mark. One slight problem that occured though is that now when I'm syncing my calendar back to what it was, it either does not search or does not find all the other calendars that I have. The list is just totally empty. Strange as it is, It does find and sync with the default [email protected] Gmail's working fine and syncing properly though.
Since I rely on the calendar I really need this to be fixed as soon as possible.
I don't want to put words in your mouths, but I figured I might need to factory reset the phone. No biggie, but a time consumer, since I need to recustomize everything again (not rooted, not titanium).
Are there any ways of luring the calendar back on track. Jumpstarting it without a factory reset?
Thanks in advance.
Henrik
So apparently all it needed was a full night of syncing, because now it works again.
It seems though that I got rid of the annoying com.HTC.bgp that drained my processor.
Thanks to the thread
Sent from my Desire HD using XDA App
Have not experienced this since the 2.3.3 upgrade, problem solved!
I'm having this problem on my Defy after installing SetVsel, setting any values, after time the cpu stuck at 100. Watchdog lite didn't show nothing but 100%, not any process higher than 50 even. I turned on in the watchdog to show system processes and ther it showed that:
init
Linux process
Had most the time the highest percent used
I googled and found this topic. The
Menu/settings/applications/development/now turn on Usb debugging.
Click to expand...
Click to collapse
solution solved my problem. The proc isn't anymroe stuck at 100%.
Hi,
I have been using my HD2 with android for a long time without too much trouble. Not long ago, while still using SD builds I would find that my phone would often freeze, this would happen almost always while surfing the web or playing games or while putting the phone under heavy load. Using nand builds the issue has gotten even worse. Every single build I have tried is almost certain to freeze during the initial setup, even if I leave it alone and give it a long time to setup and stabilize. I have been using a stock gingerbread NAND build for a week or so and it just won't be stable. It freezes during games or surfing the web mostly (though upon first installing the build, almost anything might trigger a freeze, including scrolling through a menu). I have tried task 29, and many builds but they are all giving me this issue. Even the last WINMO rom I tried did the same. I am completely baffled by this and have no idea what could be wrong. Does any one have any advise?
Thanks
Pray that you're still under warranty???
If it does it in winmo, try flashing your original stock (From HTC) ROM. This will remove HSPL and any & all customisations. Make sure the phone is in it's 'from factory' state. If it STILL has freezing issues, you need to get it repaired. If not. Start installing ROMs again from scratch.
Hope This Helps.
Thanks for the response. Yeah, I have done everything except resort to the stock ROM.
I have noticed some interesting things about the crashing behavior. If the phone has been left alone for a while, it will be able to browse the web/ play games or do intensive tasks without crashing for a decent amount of time, however once it crashes , it will very likely crash right away after I reboot. I only notice the phone (battery) is quite warm around the time it starts the crashing. I hope my hardware is screwed up, would hate to give up this phone . I bought my phone on ebay, so I don't think I have warranty either. ugh
wtf, there is seriously no one else who has heard of this?
Bump.
Are you Overclocking it? Try Underclocking it to see if it is more stable. Maybe your hardware is failing. User currentWidget to see your current usage.
Maybe you're using too much ram. o.o
The phone will get really laggy if you use up all the ram, so clear it up with a task killer.
No overclock, running at 998 (stock) and smartass governor. Tried interactive governor and still does it.
Its just strange that it crashes left and right from doing anything when I first install a build and after a few reboots it stabilizes enough to be rock solid for all tasks except playing something like angry birds or surfing the web. I tried running quadrant 10 times in a row to stress the phone and it did fine.
Could the phone be overheating? I notice its almost always warm or hot when it crashes.
poweroutlet said:
Thanks for the response. Yeah, I have done everything except resort to the stock ROM.
I have noticed some interesting things about the crashing behavior. If the phone has been left alone for a while, it will be able to browse the web/ play games or do intensive tasks without crashing for a decent amount of time, however once it crashes , it will very likely crash right away after I reboot. I only notice the phone (battery) is quite warm around the time it starts the crashing. I hope my hardware is screwed up, would hate to give up this phone . I bought my phone on ebay, so I don't think I have warranty either. ugh
Click to expand...
Click to collapse
Actually this is exactly what you should do. Flash with a Stock ROM then Take29 then start over. Remember the Stock ROM has more than just the system ROM, it overwrite your RADIO and other stuff also that are not touched by custom ROM. so if you have some corruption at radio ROM the stock ROM should fix it.
- When I mean Underclocking: set MAX Frequency to 800 Mhz and see if it is more stable. just to find the root cause by elimination
nightcraw said:
Actually this is exactly what you should do. Flash with a Stock ROM then Take29 then start over. Remember the Stock ROM has more than just the system ROM, it overwrite your RADIO and other stuff also that are not touched by custom ROM. so if you have some corruption at radio ROM the stock ROM should fix it.
- When I mean Underclocking: set MAX Frequency to 800 Mhz and see if it is more stable. just to find the root cause by elimination
Click to expand...
Click to collapse
I'll try to cap it at 800 Mhz and see if I can cause a crash. Regardless Its probably best to flash to stock rom.
Here is what I think I'll do:
Flash to stock rom.
Reflash HSPL
Task 29
Flash new radio
Flash MAGLDR
Flash new android rom
So I flashed 2.10.1 stock rom from here:
http://forum.xda-developers.com/showthread.php?t=655653
And it did not remove HSPL...though it reset my radio to 2.08.
So far things are not looking good. On the very first boot the stock winmo rom crashed and rebooted. Should I flash another winmo rom?
EDIT:
I've reflashed HSPL and also flashed the latest winmo stock rom with Radio 2.15 now. Running Android off the SD card, 2 minutes of angry birds is all it took it to freeze it. I'm starting to believe there must be some hardware damage or something, this is making no sense.
Even surfing the web in the stock winmo rom caused a reboot, the phone is getting quite hot too.
Having exact same problem... should i warranty it and send it in?
ArkAngel_X said:
Having exact same problem... should i warranty it and send it in?
Click to expand...
Click to collapse
If you are lucky enough to still have warranty, do it. I don't have that option sadly.
So I have pretty much narrowed down the cause of the problem to overheating. I let the phone cool down to about 25c and then I ran angry birds and surfed the web and it didn't crash and I played for about 15 minutes. When the temp approaches about 37-40c, the chances of a crash become pretty high, once it crashes it will keep crashing left and right until I let it cool back down.
All evidence now points to an overheating problem. Especially because it is only intensive tasks which seem to cause crashes and only the more CPU/GPU intensive tasks can cause the phone to heat up fast.
Anyone else dealt with this issue? I have no other way to prevent this than to stop heavy use of the phone when it gets warm. This is ridiculous, next thing I know, I'll be walking around with a desktop CPU heatsink mounted on my HD2...
First post WOOO
I have been having a similar issue with my HD2 (Telstra). I was running darkstone on the SD card but occasionally my phone would freeze then I would have to restart a few times to get it working (or leave it for a while). I decided to install the android desire stock ROM using NAND. I changed the radio according to the recommended 2.15.50.14.. after I did this I had a lot of problems with frequent freezing even before installing the new ROM (so during the process). I did successfully install the stock ROM but I now have the issue where if I enable internet usage within about 5 minutes my phone will freeze (but only if I am using the phone). However if I use wi-fi or usb tethering I can use the net for anywhere between 5 minutes and 8-9 hours.
I also have the problem of freezing just after boot, but apart from that my phone has never frozen unless I enable internet usage. Furthermore, this issue only became frequent after changing radios. (for the life of me I can't remember what the previous radio was). When I have more stable internet access I'll try flashing a few different radio's...
But right now funnily enough.. I'm jumping between my phone internet and someones open network in my apartment block... both of which are very sporadic...
Hope this helps somewhat (or will at least..)
There are many threads regarding this issue. If you still have the problem after trying different radios and roms, then it is probably the mainboard.
Mine was also overheating and after I tried all possible fixes, I sent it for repair. They changed the mainboard and everything is OK now. No overheating at all.
Okay, this is getting ridiculous and im getting pissed. My N10 has been working without a hitch (and without a camera flash too) for the past 6 or 7 months since i got it but one thing that is happening now is getting very annoying is it just exits out of apps when the app is trying to load something...not exiting when the app itself is loading, but when the app is busy loading another task. Man im getting mad...so for example im on facebook the interface loads fine but when i start browsing pictures and an image is taking a few seconds to load and BAM, the program closes, another example i have the AOSP browser opened and im browsing the web, I type in a web address it starts to load, and BAM, closes, playing candy crush, it plays fine and then i try to ask for help from facebook and once it starts loading my friends and it does it again.i could go on and on. its happening on game apps, google apps its pissing me the heck off and it just started about a month ago. I have tried several roms thinking it was a memory leak somewhere or something for that matter and no luck. Ive tried trinity and KT kernels thinking the stock kernel was the culprit and still no dice. Ive even gone as far as to wipe out the whole device, everything to the fullest system format and reinstall a new stock image via wugs toolkit...still happening. Can anyone tell me why this is happening and is there a fix for this? Is anyone going through this crap too? The Dev forums have been quite lately but im sure this tablet still has very active users who can help because this is getting old. BTW I am running Purity latest rom with Franco kernel r12 just in case you need to know
Does this happen after you watch videos? For me, that's the only time..apparently the surface flinger eats up the RAM and hardly 20-30MB is left for other apps. So I guess the system starts force closing the apps. I don't think we have a permanent fix for this yet. However, the workaround I have applied is I disabled Chrome which is another RAM eater and since then this random force closing and even the random restarts problem seems to have been alleviated!
Another simpler option is to restart the tab whenever you feel it is starting to operate with a lag. Takes hardly 30 seconds And hope for Google to release the fix to the surface flinger issue with 4.3!
Sent from my Nexus 10 using xda app-developers app