Topic: temp freezes in iceweasel

Did a number of searches but couldn't find this exactly.

Everythign appears to be working fine, but on occasion, maybe once or twice a day, iceweasel will stop responding for about a minute, then it'll start working again like nothing happened.

Iceweasel doesn't appear to be doing anything at the time, but if I try to scroll the window, or click on a link in the page, or go to bookmarks to open a  new page, nothing.

The rest of the system is responsive, so I switch to another program until I see that iceweasel has done what I told it to do.

It isn't stopping me from doing what I want to do, but it is very frustrating.

What can I do to try to pin down what is causing the freeze, or better yet, what can I do to prevent the freeze?

Thanks,
David

PS. On very rare occasion, I will see the same thing happen in icedove. But I haven't noticed it with any other programs.

Re: temp freezes in iceweasel

you can start iceweasel from the terminal window (OPenbox or XFCE menu -> Terminator/Termincal -> simply enter iceweasel or iceweasel-bin or firefox - dont remember which one), keep the terminal window open in the background, and as soon you notice a freeze, you go over to the terminal, wait until it is OK again and Press Ctrl-C.
if there is some output (above "Terminated" or "Aborted") you might copy and paste to post it here and we take a look.

EDIT: please also tell us if and which Add-ons or Styles you are using in iceweasel (if any) and maybe additionally: enter about:plugins in the Adress bar of iceweasel and post the content here (simple copy and paste will do)

Last edited by machinebacon (2010-10-17 12:57:21)

Let's all get forked.

Re: temp freezes in iceweasel

Don't you just hate when you sit there suffering with a problem, and post to a forum to get a solution, and... the problem just goes away on its own. In the past week, I have seen the temporary freeze maybe once, and that was when the disk was churning away, so I'd expect a delay.

So know more problem - at least at this time.

I did find messages when I ran the browser through a terminal:

(firefox-bin:20922): Gdk-WARNING **: XID collision, trouble ahead

From a Google search, apparently this is a known issue with firefox/gtk, with barbs traded back and forth on whose bug it actually is. One sentence in one bug tracker suggested it could cuase delays like I was seeing, but it would more likely crash the system.

David