* Helge Hafting ([EMAIL PROTECTED]) wrote: > Package: iceweasel > Version: 2.0.0.12-1 > Severity: normal > > > I sometimes read the newspaper at http://vg.no > My way of reading is to right-click each interesting article and > select "open in a new tab". That way I quicly finish reading all > the headlines before reading each article. > > But - opening 5 os so tabs make iceweasel very slow, and 10 tabs > makes it lock up for several minutes at a time. Using --safe-mode > is no better. > > This is not a network or linux swapping problem. The pages finish loading > quicly, but the cpu is stuck at 100% - iceweasel works and works > and accomplish nothing. The problem comes quickly, I open another > tab and notices a slowdown - then I know that opening one more tab > will kill performance completely. > > The pages uses lots of graphichs and animated ads - so I wouldn't > complain if a single page was a little sluggish. I see no reason > why loading many such pages should bring iceweasel to a halt though. > > After all - only _one_ tab is visible at a time. So there is only one > set of animations to run at any time. My computer is cabable of doing > that. The other pages should simply be put on hold until viewed. > > > > Upping the iceweasel cache from 50MB to 500MB seems to help, but only > some. Iceweasel is sluggish, it switches between tabs using > "only" a few seconds each time - then it locks up with 100% cpu again > and is stuck for enough time to let me write this bug report. > > > If this is a cache issue - please give the viewed page priority in > cache. Don't let the invisible webpages cause cache trashing, if they > need more memory, just stop processing them until viewed. The > performance of that approach should be no worse than viewing the > pages sequentially. > > Also - when iceweasel is "stuck", the animations on the page being > viewed runs all the time while the rest (html, images) isn't > updated at all. How about not wasting cpu on animation _at all_ until > the page is fully rendered? Until the switch to a different tab is > completed? > > I know iceweasel processed the click on the new tab - because the new > tab is highlighted. So why is the animations for the old tab still > running, wasting cpu power that iceweasel seems to need for bringing up > the new page? Freezing/abandoning such processes ought to be among > the first things to do. > > > Finally - thanks for making this fine browser. I hope these performance > issues can be sorted out though. The pc is not underpowered - I can read > (and render) 10 of these pages sequentially in much less time than > the time iceweasel is stuck when trying to load them all simultaneously. > the simultaneous case shoudln't take more time than the sum > of the time needed for individual pages, as long as the pc and linux > have enough memory.
Any better in Iceweasel 3.0? -- Eric Dorland <[EMAIL PROTECTED]> ICQ: #61138586, Jabber: [EMAIL PROTECTED]
signature.asc
Description: Digital signature
