-
All replies
-
Helpful answers
-
Dec 1, 2013 5:22 AM in response to carrierjasonby Csound1,Ram, or disk space?
What are you actually doing?
-
Dec 1, 2013 1:16 PM in response to REPGby richardfromcascais weymouth,I found inkjet9 related to HP desk jet 3050 j610 using .48 gigs of memory probably it was trying to internet print a job I killed inkjet9 and now it is all ok
-
by Drew Reece,Dec 1, 2013 2:04 PM in response to richardfromcascais weymouth
Drew Reece
Dec 1, 2013 2:04 PM
in response to richardfromcascais weymouth
Level 5 (7,808 points)
NotebooksI have seen inkjet9 mentioned here in another troubleshooting thread (searching 'inkjet9' may find it). I think the suggestion was to delete the printer & recreate it.
Otherwise remove the drivers, they seem to cause trouble on 10.9 look for updates if you require them.
-
-
Dec 8, 2013 6:06 AM in response to Reddpercby Robert Maziarka,Mavericks! Seems that there are a ton of people with the same issue. After about 10 minutes, all my aps are "paused". Let me know if you find a solution.
-
Dec 8, 2013 6:32 AM in response to Robert Maziarkaby Drew Reece,You are going to wait for one user to fix your Mac?
Reddperc posted here once in October, do you think waiting for them to tell you anything is a good idea?
Create your own thread, describe your issue, post an EtreCheck report, get you issue looked into…
Otherwise keep waiting for a user who hasn't replied in over a month and may well have different issues…
-
Dec 8, 2013 7:31 AM in response to Drew Reeceby Kenneth Collins1,Because Mavericks has a new method of managing memory (compressed memory), it is likely a low-level bug that wasn't apparent or wasn't a show stopper in the beta testing.
Apple has a lot of incentive to fix it, not just because of the number of affected customers, not just because of the number of affected Apple managers, and not just because this is a bug in a feature they bragged about in advertising, but also because Microsoft could make a commercial out of the error message if the bug persists.
The developers have their feet to the fire and they might even be working overtime and under pressure. They have to identify the problem in detail, find the cause, make a fix, and test the fix to make sure they aren't swapping one bug for another. It will probably be fixed in 10.9.1 or 10.9.2, depending on how difficult it is.
They have my sympathy. Let's just fidget impatiently until they are done.
-
Dec 8, 2013 7:32 AM in response to Robert Maziarkaby carrierjason,I really hope Apple fixes this, I set up a script to kill the iPhotoshare process which seem to be cuasing me the issue. However the machine is no where near as useful as it was Mountain lion. I also know the Mavrick was free, but I would rather pay, than have issues.
I may end up buying a new machine, but I really wanted to get another year out of it.
-
Dec 8, 2013 11:06 AM in response to Kenneth Collins1by Drew Reece,Kenneth Collins1 wrote:
They have my sympathy. Let's just fidget impatiently until they are done.
Good luck with that! Fidgeting never fixed anything, I don't see how waiting for Apple to create a fix is a good choice, which release do you wait for 10.9.1, 10.9.2… ?
carrierjason wrote:
I really hope Apple fixes this, I set up a script to kill the iPhotoshare process which seem to be cuasing me the issue.
Have you looked at logs to see if other processes are part of the issue? How about finding out how to turn that feature off instead of killing processes with a great big hammer?!
How about all the other installed software? Have you tried safe mode, a new user account or disabling login items? How about fixing any disk damage in recovery mode?
Seriously both of you should stop 'hoping for fixes' & post EtreCheck reports so you can try resolving your issues (create a new thread & detail your issues). There are many reasons for Macs to misbehave. Sitting on your hands won't change anything unless you are lucky
Why are you assuming Mavericks is the only reason for issues, these boards are littered with posts from people whose Macs improved after deleting/ updating old software.
-
Dec 8, 2013 11:17 AM in response to Drew Reeceby Kenneth Collins1,It's not unusual for the first release to have a code pratfall in it that is fixed in the point one release.
What you say makes a lot of sense. It happens very rarely for me, and I only recall Mail gumming up the works. I wouldn't know what to do with the information in Console, but I can try the other things.
-
Dec 8, 2013 11:26 AM in response to Kenneth Collins1by Drew Reece,Yes, you are correct about initial releases, they do often have major issues but many are not seeing that so it suggests…
Mavericks + something else = problems
I (and many others) will help you look at what is installed or try isolating the issue(s) (via safe mode, disk repair, logs … whatever is appropriate to YOUR issues) if you can explain what behavior you see and provide a report it will help. A new thread will stop some of the 'crosstalk'.
-
Dec 8, 2013 11:32 AM in response to REPGby Michael Haffey,I've used EtreCheck and managed to clean up some stuff.
However, I started using Apple Mac 10 years ago and what I have now has migrated from one machine to another and one OSX to another over that time and there is some accumulated debris which I can't find or figure out.
I'm wondering whether it's time to do a clean Mavericks install and re-install all the apps. I have the necessary product keys and Time Machine backups of data.
Thoughts?
-
Dec 8, 2013 1:14 PM in response to Michael Haffeyby Drew Reece,There comes a time when breaking the links to years of migrations is the safest bet.
10.9 currently has issues with older kernel extensions & startup items etc. As you learned from Arthur.
Starting fresh might be a good idea if you are willing to take on the work of re-installing apps etc. You may also find what data and apps are important to you. Keep a rough record as you add apps & then if you hit a decrease in performance you can undo those items.
Personally I prefer to take a bootable clone of a system, just incase I need to boot back into it to find where a particular file lives (or to complete a task in an old app) etc. I use Time Machine for those 'oops did I really delete that?!' moments.
-
Dec 10, 2013 8:36 AM in response to REPGby Kieron Edwards,Any one else running a HP printer and seeing the Inkjet4 process growing at an alarming rate? There are other threads on this forum discussing this particular issue.
https://discussions.apple.com/thread/4910797?tstart=0
I booted and it was using 148MB - it's just about to top 1GB and no one is using the printer. Nothing in the queue either.
-
Dec 10, 2013 9:09 AM in response to Kieron Edwardsby Da O,Hi Kieron,
I posted a couple of weeks ago on this thread with the same problem but then, as am still running ML was told to start a new thread as this was for Mavericks. The reason I am responding here again is that after following both threads for the past 2 weeks I see a convergence of a problem first mentioned in March of this year with ML. What I have observed from others: Somehow the print function, whether it is in ML or Mavericks, and whether it is HP inkjet process or as in my case under-IP (wireless HP printer) catches a spooled job and then without notifying us that the job is spooling or still in the queue, begins to eat memory until the machine runs out and has be rebooted. After much investigative work and finally tracking this process down, I have been running Activity Monitor in the doc and periodically I check to see if the process has restarted itself and if so I force quit it, and voila, memory returns.
I repeat I am responding to this here because I have now seen that this is a ML and a Mavericks issue and most probably points to a HP/Apple and possibly OS print software bug. The fact that it started in ML and continues in Mavericks most probably means that it was not given attention in the upgrade. Perhaps now, it will be and fixed for all of us.