Navigate / search

Inkjet9 and cupsd runaway processes

Today my computer was running hot all day, fans buzzing wildly.  Honestly I didn’t think too much of it since I was working with the iPhone simulator and just assumed that that was the cause.

After taking some time off to play with the dog, I came back to it still buzzing loudly.  I checked my iStat Menu to see what processes were taking up the most resources and saw ‘cupsd’.  Google told me it was related to my printer.  But I couldn’t kill the process for the life of me.  I tried killall, kill -9, and the activity monitor.  Nothing.

In activity monitor I saw another process Inkjet9 that was taking up even more resources.  And there were two of them!  Google didn’t have anything to say about Inkjet9.  I couldn’t killall or kill -9 this one because it didn’t show up in my ps -A.  I was able to kill it in Activity monitor, but it just respawned.  And to top it off, restarting my computer didn’t help either.

Uh oh … I’ve been hacked.  At least that’s what my initial thought was.

What I did find with my ps -A was a few print jobs that I had sent off this morning to my wireless HP printer.  Yup, and they had never printed.  I was able to kill all the specific print job related tasks and that took care of the rest of the runaway processes.

It is a good thing my aging laptop didn’t fry after running hot for some 8 hours.  Eh, then I could’ve bought a new one… hah.

Anyway.  Since nothing showed up for my Google on Inkjet9, I wanted to write a little post incase someone else had the same random problem I did.  It makes me scratch my head why Inkjet9 showed up in iStat Menu and Activity Monitor but not in ps -A.  I have no idea.

Hope this helps!

Comments

swim guy

inkjet9 is coming up in my activity monitor continuously. i have wireless hp printer but nothing in que.

my printer is slow and running hot! i didn’t understand all the kill commands but do you have any other suggestions?

Jason

You didn’t understand the kill commands or they didn’t work?

When you open terminal you can type ‘kill’ commands.

Here’s the steps to follow:

1.) type ‘ps -A’ and look for any processes, probably near the bottom, that have words like HP, printer, or document names that you recently tried to print.

2.) There will be a process number on the far left column. Let’s call this number 12345. You would then type the following command: ‘sudo kill -9 12345’.

3.) Type in the admin password and you should be good to go.

Hope that works. If not, write back and we’ll brainstorm.

Jason

Paul

Thank you for your posting.
I got exactly the same problem with Inkjet9 process.

Do you have any idea how to permanently fix this?

Jason

@Paul Unfortunately I do not. Honestly it really might be some type of malware… but maybe I am just paranoid. My experience with my wireless HP printer always has a few thunderstorms mixed into mostly sunny days. The number of thunderstorms that cause runaway processes does not seem to be that large though… so I haven’t put much thought into a permanent fix.

My post might be a little dated, but glad you found it helpful. If you find anything additional on the interwebs, let me know and I’ll update my post!

Fearn

Just had the same issue, had an Inkjet9 process listed in iStat as taking up 855MB, turned out my D&D character sheet was sat in my print queue for some reason. Thanks for posting this, it was the only relevant hit I got!

Soufiane

Thank you !!

Robin van Baalen

Thanks man! Very helpful. My initial thought was exactly the same: shit I’m hacked / I got a virus.

Fired up my Mac Mini this morning only to discover that the memory monitor said “100MB free memory / 7900MB used memory”. And there it was. Inkjet9 consuming almost 4GB of memory!!?

giyad

+1

George K.

Thank you for the write up. I did help me. I have Mac OS 1.0.7.4 and I just went to the print queue in the settings. There i saw 4 print jobs waiting to be printed while my printer was off. This job took 5 GB of my memory! After deleting the print jobs in the queue, that 5 GB freed in the memory.

André

Thanx man! Just had the same issue…

Leave a comment

name*

email* (not published)

website