Problem with stock web browser

[ziggazee]

The web browser keeps crashing, some times it will crash after a while of using the browser other times it will crash upon opening the web browser. So then I have to use the task manager to exit from it. It usually keeps crashing if I try and open the browser again, In the task manager it says (in red writing) the browser its using around 60% of the cpu? Anyone else having this issue? Btw I'm running the latest firmware KE7, don't remember it happening in the earlier firmwares.

Sent from my GT-I9100 using XDA App

 

[madmack]

The web browser keeps crashing, some times it will crash after a while of using the browser other times it will crash upon opening the web browser. So then I have to use the task manager to exit from it. It usually keeps crashing if I try and open the browser again, In the task manager it says (in red writing) the browser its using around 60% of the cpu? Anyone else having this issue? Btw I'm running the latest firmware KE7, don't remember it happening in the earlier firmwares.

Sent from my GT-I9100 using XDA App

interesting, are you on stock KE7 ? not one of the custom roms ?

Sent from my GT-I9100 using XDA App

 

[ziggazee]

interesting, are you on stock KE7 ? not one of the custom roms ?

Yep stock rom, its weird I just opened the browser to check how much of the cpu it uses just after the browser has been open and is still on the homepage (which I have set as google) and its was already displaying in red around 40%. how much cpu does your browser use after opening?

Sent from my GT-I9100 using XDA App

Sent from my GT-I9100 using XDA App

 

[madmack]

when the browser is working, 0%.

I'm interested in this though because I compile my own browser web core and so far I've been struggling to make it robust. similar symptoms, 46% CPU utilization when it crashes. I thought the problem was with my compilation setup, so I'm kinda happy to see it isn't entirely my faulty core and that it happens with the stock rom as well.

hope Samsung fixes this ! I have no idea why it happens but in my case it seemed it was a problem with the prelink and linker setup. never gave stock browser a fair chance to test it rigorously as I do with mine.

Sent from my GT-I9100 using XDA App