Fred Smith wrote: > On Tue, Feb 04, 2014 at 02:31:51PM +0000, Laurent Wandrebeck wrote: >> Fred Smith <fredex at fcshome.stoneham.ma.us> a écrit : >> >> > Um, it appears in the process list as "ImageDecoder". I don't know how >> > one would determine that it's java or not. <snip> > here's some output from top (with ppid and thread id added): > > 23040 fredex 20 0 2424m 1.2g 41m S 0.3 16.3 1:13.71 1 fredex > ImageDecoder #1 > 23123 fredex 20 0 2424m 1.2g 41m S 0.3 16.3 1:12.82 1 fredex > ImageDecoder #2 <snip> > it appears to be a child of init, since PPID is 1 (the column just to the > left of "fredex".) Suggests that they crashed, or logged out, and this remained running. > > given that "ImageDecoder #1" is process 23040, doing "ps -eLf | grep > 23040" reveals: > > fredex 23011 1 23040 0 40 Feb03 ? 00:01:13 > /home/fredex/myfiles/programs/firefox-19/firefox/firefox > > It appears to be some kind of firefox alias, though I don't understand > that relationship... <snip> > so, Firefox has spawned a ton of child threads, and some of them appear > in top as "Image Decoder #x". I dunno WHY they have a strange name, > but at least I now know where they came from. <snip> > So, I guess this is solved as far as I feel like taking it. Thanks to all > (both) of you who offered advice. One more thing before you drop it - it is, in fact, a firefox thing, and based on the name, either java or perl.... <https://bugzilla.mozilla.org/show_bug.cgi?id=860149> (after googling firefox imagedecoder). mark