[Pkg-chromium-maint] Bug#669338: "chromium --service" launched from kde startup file eats 100% CPU

[David Baron]

>  (Is memory usage high when the problems happen?
Yes. 100% of my 2gig (OK, I should get more) is eaten.
The disk activity led is also almost steady.

>  How do you
> know that it is chromium that is misbehaving?)
As I said, it might not be.

Chromium can trigger the problem, likely the flash, but I have had it occur 
with no chromium instance running at all. Without chromium, however, the 
problem MAY be briefer and pass. It chromium is running, I have to go into a 
console and kill all instances or else hit reset.

The flag I reported on the tty was not from the UPS--this had been moved to 
USB. When the problem occurs and I can escape it, the NUT monitor pipe has 
been broken and I must disconnedt/connect to stop the notifications and use 
the NUT applet.

An external modem is connected to the tty without problems.

> > INFO: task recollindex:613 blocked for more than 120 seconds.
> > "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
> > recollindex     D 00000000     0   613      1 0x00000000
> 
> [and again at other times]
> 
> Do these events coincide with the periods when chromium is busy?
> 

Cannot say for sure but with 100% of two CPUs and 100% of memory tied up, that 
would make sense. I have seen the recollindex ask for amounts of memory and 
their could be a bug in the latest version but I do not know.