Ever since I upgraded to galeon 1.2.6 and mozilla 1.0.1 I can repeatedly lockup galeon, ro cause it to max out a CPU. To duplicate a lockup/cpu hog, clickon a download select wher to save it (I use my home dir), and them after that starts immediately click on some other link to a different page. On my box it will typically hang the browser completely. Teh file transfer stops and hte window fails to redraw and CPU usage forthe "galeon-bin" process goes to 100%. Sometimes tis listed as user time, others its listed as system time (via gkrellm-2.0) to cause the browser to east 100% but not hang, you do a similar thing to above, except instead of clicking on a link after starting a download, you open a new tab and then opne ANY url. This thows my galeon up to 100% usage, and choppy performance from then on. The downoad will reach 99.9% but not close. an "strace" on the cpu hoging galeon-bin shows its sending SIGTERMs to one of its own processes. (thread?) the process doesn't die, killing it manually causes the whole browser and all threads to close(die)
Using galeon 1.2.6 nad mozilla 1.1-r1 and I can't duplictea this.
Well it doesn't look like a gentoo bug to me anyway.
