Browser Lock-ups

[rickytenzer]

I just installed the new chromium build after cleaning up all the files in my applicationdata folder for chrome and chromium, and I've yet to have a freeze. Crossing my fingers...

Still working fine...

[Dusenberg]

I'm a Chrome newbie and thought I should pass on my experiences.

I have just installed Chrome in the last week on XP (SP2) on my desktop and on Ubuntu 10.04 on my laptop. We watch a lot of BBC iPlayer (Flash) and their latest update runs jerky on FF on both OS so I was looking forward to see if Chrome ran faster/smoother.

First brief try of iPlayer on the laptop was brilliant - fast, no jerks. So I installed Chrome on the PC (which incidentally has latest Adobe version) and tried iPlayer... Within 3 minutes it froze the whole system.... after reboot I removed Chrome and went back to FF.

Back to my laptop .... this weekend I was watching MotoGP in trouble free smoothness until after 29 minutes it froze the whole Linux system and I had to reboot - that has never happened before in over 3 years with ubuntu...

I checked the forums and saw there is obviously a very big problem with Chrome and Flash and no solution so I removed Chrome from the laptop as well.

I had other relatively minor problems with Chrome, particularly bookmark import not working on both platforms. I am happy to work with minor probs like that on new software, but without stable Flash playback Chrome is useless in this house

I'll keep watching for improvements though....

Cheers

[loqk]

after years of this trouble, it seems likely that this is a problem with the sequence of accessing a tab with lowered priority.

it seems that any tab that has below normal priority will lock up your computer in proportion to the speed of your processor.

once you click on the tab, the tasks seem to be these:
1:activate tab
2:display tab images
3:set priority of tab to normal

since the first two tasks are performed at low priority, they happen slowly, but, due to some resource conflict, all of the windows interface is locked until the page finishes loading.

on faster computers this happens faster and is less noticeable. on slower computers, this can take 10 seconds or more, usually in the middle of active control of the user, completely interrupting work flow. it also seems to stop network traffic and prevent video playback leading to a looping of the video sound until the page is fully loaded and the priority returned to normal.

this effect can be eliminated by setting all chrome threads to normal priority. unfortunately, since chrome seems to have no way to turn off the automatic downgrading of priority, this must be done manually for every thread (chrome instance).

it seems that this would be easily fixed by setting the priority to normal, pausing to allow windows to implement the change, then activating the window. i assume there is some technical reason this was not done or has not been implemented in an update.

however, there is no excuse for forcing the user to put up with this problem when it could also be fixed by adding a button that stops the downgrading of process priority, or setting it to normal instead of below normal at the moment the page would normally be set to below normal priority.