[eddiecatflap]

i installed it on my imac , suddenly all my 768 mb ram is used up with no programs running

and my 80 gig hd that had 12 gigs free last night suddenly filled up 100 %

i deleted 10 gigs a few hours ago , restarted , came back to the mac and found it's now got only 6 gigs free

any ideas ??

[Hi I'm Ben]

Oh well.
my iBook didn't even notice I installed it.

[eddiecatflap]

this is getting ridiculous

my free hard disk space !!

it's literally vansihing in front of my eyes

it started at 6 gigs free

now , 10 minutes later it says 5.93

what can be wrong ???

please help !

[Kenneth]

I ran the update on both of my Macs;
1) DP 1.25 PowerMac G4(FW800)
2) Original iBook 300

I repaired permission on both Macs before running the Software Update. So far, I didn't notice any problem on eating up RAM and storage space.

[eddiecatflap]

this is spooky

now it's back to 17 gigs free but all my ram's used up under the activity monitor

has apple fundamentally changed the vm in os-x ?

should i take it in to be looked at ?

[Ganesha]

No ram issues here. See if anything running has a memory leak.

[eddiecatflap]

sorry to sound dumb , how does one do that ?

[FredTheDead]

I saw on the IMG forums that the problem you seem to be experiencing may be caused by a bug with the driver for Macally's iShock gamepad. Would you by any chance happen to be using that?

Otherwise, try opening Activity Monitor (in the Utilities folder). It might give you a clue towards what's eating up your RAM and disk space.

- Fred

[eddiecatflap]

yes !

thanks

i joined the discussion and it IS the macally ishock driver

if you're using 10.3.8 - disable it asap

it uses up all your ram , cpu and hard disk space !

weird bug or something

http://discussions.info.apple.com/[email protected]/8

[macaddict0001]

what if you use the gamepad with just mac osx's built in drivers? does it cause an issue then?

[turtle777]

Originally posted by Ganesha:
No ram issues here. See if anything running has a memory leak.

Originally posted by eddiecatflap:
sorry to sound dumb , how does one do that ?

Little greenish puddle on the floor, maybe ?

-t

[turtle777]

Originally posted by eddiecatflap:
weird bug or something

That sounds like the good old HP Printer/Scanner/Copier drivers.
Same sh!t.

-t

[eddiecatflap]

i got this from macfixit !

"Issues with MacAlly iShock driver MacFixIt reader George Wagner reports some serious issues apparently caused by the driver for MacAlly's iShock (a programmable USB game controller).


Goerge writes:


"Downloaded the combo update and installed. On restart, my drive space dropped by almost 4GB immediately, and within minutes lost another 350MB or so. Trying to check the system log hung Console, so I suspected something was generating huge numbers of error messages. Activity Monitor showed that the MacAlly iShock driver was using as much CPU as it could get its hand on and my CPU was pegged at 100% with fan running constantly. I killed the iShock driver and deleted the (extremely) bloated system.log file. This seems to have solved the problem and the system has been stable since. I reported the broken driver to MacAlly, but I don't get the impression that they're very fast about update things."

[SMacTech]

Originally posted by eddiecatflap:
i got this from macfixit !

"Issues with MacAlly iShock driver MacFixIt reader George Wagner reports some serious issues apparently caused by the driver for MacAlly's iShock (a programmable USB game controller).

And one bad driver makes 10.3.8 a bug laden mess? The sky is falling yet again.

[Footy]

Had this same issue last night after updating to 10.3.8. My HD filled up very quick. Got a warning message that my HD was almost full right about the same time I noticed my system was a bit laggy. Only had about 130 MB left of about 10 gigs I had free when this happened. Needless to say with in minutes that was gone too and it was asking me if I wanted to shut down the Finder.

I was able to drop all important file on HD 2 no problem and I just zeroed HD 1 and dropped a fresh install on it. Nice fresh install of the OS is nice but things were pretty frantic there for a bit.

And yes I have an iShock! Won't be using that anytime soon.

[Webscreamer]

Originally posted by SMacTech:
And one bad driver makes 10.3.8 a bug laden mess? The sky is falling yet again.

Don't you love when one 3rd party app is broken and people say it's a terrible update? Apple doesn't write software to make 3rd party stuff work and compensate for it's poor programming. 3rd party software is written to work on Apple's system.

If you would run a clean install of OS X with 10.3.8 on it, I guarantee you it would work fine with no 3rd party crap on it. That's all Apple's responsible for.

You pissibly should have named the subject "10.3.8 and iShock Incompatibility"

[eddiecatflap]

well , i didn't know it WAS that when i wrote the thread , did i ?

[Webscreamer]

Originally posted by eddiecatflap:
well , i didn't know it WAS that when i wrote the thread , did i ?

You had one issue, not a list of 25 bugs that popped up after 10.3.8 was installed.

[Big Mac]

Originally posted by Webscreamer:
You had one issue, not a list of 25 bugs that popped up after 10.3.8 was installed.

He had no issue with the driver before and didn't realize what the problem was until someone replied with the information. It's wrong to jump conclusions like eddie did, but he shouldn't be vilified for it. Maybe the mods can rename the thread.

[Recto Bold]

Originally posted by eddiecatflap:
well , i didn't know it WAS that when i wrote the thread , did i ?

You didn't know it was a "bug laden mess" either.

[Phil Sherry]

ridiculous.

[lenox]

preposterous!

[jasong]

Ludicrous!

[Simon Mundy]

Poppycock. Absolute piffle.

[eddiecatflap]

ok , ok , i apologise



10.3.8 is excellent

but macally 100% suck

hows that ?

[Wiskedjak]

I don't run updates anymore unless absolutely necessary. And even then, I wait several weeks to see if there are any reports of problems on machines similar to mine.

At least M$ updates repair flaws in the OS ...

[SMacTech]

Originally posted by Wiskedjak:
I don't run updates anymore unless absolutely necessary. And even then, I wait several weeks to see if there are any reports of problems on machines similar to mine.

At least M$ updates repair flaws in the OS ...

ummm, OK. You want a list of flaws still NOT fixed in XP, or any of Microsoft's other product updates.

[Wiskedjak]

Originally posted by SMacTech:
ummm, OK. You want a list of flaws still NOT fixed in XP, or any of Microsoft's other product updates.

I didn't say that M$ updates fix all flaws, just that they at least don't create new flaws.

[SMacTech]

Originally posted by Wiskedjak:
I didn't say that M$ updates fix all flaws, just that they at least don't create new flaws.

OK, now your digging your hole even deeper. Being a sys admin, I can tell you that they do indeed introduce them. I don't care if it is Linux, OS X, XP or any of its variants.

Why do you think we test the updates before placing them into production? It's to ensure there are no NEW bugs.

So you are saying that the latest update of Mac OS X didn't fix any flaws? You certainly said nothing about it introducing new ones.

But you can run 10.0 too, as you won't find any of the bugs introduced in 10.1 - 10.3, nor will you benefit from the fixes you state Apple doesn't make.

[Wiskedjak]

Of course, I know that it is impossible to be critical of Apple among the faithful, but as a user, I have had FAR fewer problems with Windows updates than I have from OSX updates.

[jasong]

Originally posted by Wiskedjak:
I didn't say that M$ updates fix all flaws, just that they at least don't create new flaws.

So where did all those flaws come from then? They created their version of DOS in 19-whatever with a billion flaws that they are still fixing today, but have never added a new flaw?

I've had no problems with 10.3.8 on two machines (including my hacked Beige G3. But then I am an Apple apologist, so I get the special version without the debug code or fatal flaws.

Membership is free, you just have to drink the Kool-Aid

-- Jason

[Boondoggle]

Originally posted by Wiskedjak:
Of course, I know that it is impossible to be critical of Apple among the faithful, but as a user, I have had FAR fewer problems with Windows updates than I have from OSX updates.

Well to be fair many of us have had zero problems with this and all other OSX Updates, myself included. So far I have updated 4 systems, all different, with zero problems.

I do however take the following precautions with all updates:

1. Repair Permissions before and After Update.
2. Always Use Combo Updater.
3. Unplug any Firewire or other External devices.

[eddiecatflap]

look guys , i allready said i love apple 100% and bill gates sucks

wot next ?

my 10.3.8 is 100% ok now

i blame macally totally

[SMacTech]

Originally posted by Wiskedjak:
Of course, I know that it is impossible to be critical of Apple among the faithful, but as a user, I have had FAR fewer problems with Windows updates than I have from OSX updates.

It is quite possible to be critical, and a lot of us do it. Even I stated in my above post that OS X [ and others ] will have its update problems.

eddiecatflap : you don't have to proclaim your love for apple or infer what bill does to gain acceptance in the Mac community. My only suggestion would be to use a more reasonable approach to trying to get your problem solved then resorting to misleading thread titles and unfounded presumptions.

Others coming to the forum, read the thread title's and go running scared because of it for no fault of the update, just some company's shoddy driver coding.


However, glad to see your problem was diagnosed and fixed.

[MilkmanDan]

That weird iShock issue ate up 26 GIGs of space on my Popwerbook. Good lord!

[MacmanX]

Great Gigabyte's Ghost, Batman! That was one freakin' scary little bug. However, I must say it's the first bug I've ever found the solution for before realising I had the bug.

I just updated before going out for coffee. I was hanging out when I saw this thread. Just as I was reading what caused the problem, whamo, out of disk space error. Thanks for the link to Apple's discussion! I had my problem solved within 5 minutes of knowing I had one. For my first major update bug, it certainly was squashed quickly.

Cheers!

[machineknight]

Yeah, totally had the same problem. YARRRR. and after freaking out for like 1.5 hrs, I finally figured it out (with the help of everyone's threads in various mac forums)

So after a bazillion and a half restarts... ok ok, more like 4 restarts,.. and after "killing" the ishock processes and thinking I had deleted the system.log, I sat down and read every single thread (and their digressions) related to this topic. Finally I took all the unix commands given to me and just fiddled around in Terminal. The hardest problem for me was FINDING THE FRIKKIN ISHOCK DRIVERS.

So for any other person out there who has this problem and is too lazy to look up other threads about it... here's step-by-step directions. I call it Operation GIVE ME BACK MY FREE SPACE!! YARRR!!...

1 - freak out and cry like a baby. it helps. really.
2 - continue reading this. and wash your face, crybaby! hehe
3 - DELETE ishock drivers. FIND THEM HERE: macintosh HD/Library/Application Support/ (cuz by the time you've flipped out, you'd have realized trying to type in 'ishock' into the 'search' window won't work and will crash your Finder...)
4 - Empty the trash!
5 - Open Terminal (macintosh HD/Applications/Utilities/) and type in the following: (each new line means new command)
cd /var/log
ls -l
[[ LOOK FOR THE PROCESS WITH THE LONGEST BUNCH OF ##'s... for me it was like 220099338575 - it should be associated with a file called system.log or system.log.## ]]
6 - Now that you've found the culprit, type this:
sudo mv system.log xx (if its system.log.#, then type that in else it wont work)
sudo rm -f xx

(you might get prompted for a password. put it in!)

REAP THE BENEFITS OF SUCCEEDING IN THE OPERATION!!

yay! huzzah! woohoo! etc etc.

much much much thanks go to all the people who posted info/help on this in different threads in diff forums (incl. this one)

peace out.

[MilkmanDan]

Man, I killed the iShock driver, and then deleted the log files to give me back my 26.26 GIGs of space. Oddly something is still taking up all my CPU power and activity monitor doesn't even show me what it is. Any ideas?

[Love Calm Quiet]

This is sounding like so much fun. (such good terminal practice)

Can anyone recommend a place to go and *NOT* buy a McNally iShock ?

[eddiecatflap]

altho' something is def. eating up all my ram

in activity monitor in 10.3.7 and earlier i always had at least 100 negs ram free now it's at 8mbs

wonder why

[ecrelin]

Check your running apps, it should all add up. But 100 free isn't much, I bet when you are really running games and stuff you are paging out madly. RAM is cheap get yourself a Gig makes it run oh so smooth�

[jamil5454]

OK, if you ever have any problems with CPU usage or RAM usage:

You can use Activity Monitor to see what the run-away app is.

OR, What I like to do:

Open up a Terminal session and (as superuser) type "ps -aux". This will give quite a bit of information on the running processes, including their PID. Then use "kill [PID]" to kill that process. If it won't die, try typing "kill -9 [PID]". That sends the process an unavoidable KILL signal and will kill the process 100% of the time. Be careful with this one.

You could just type "top". This basically just a program that puts the output of "ps -aux" into a nice readable format.

[jasong]

Originally posted by eddiecatflap:
altho' something is def. eating up all my ram
in activity monitor in 10.3.7 and earlier i always had at least 100 negs ram free now it's at 8mbs
wonder why

You don't want any free RAM. Free RAM is wasted RAM.

Now, if your system is swapping out to disk uncontrollably, that is an issue.

-- Jason

[Wevah]

Originally posted by eddiecatflap:
ok , ok , i apologise



10.3.8 is excellent

but macally 100% suck

hows that ?

Their drivers, yes.

I still like the actual iShock controller better than any other USB controller I've used (though hooking up a real PlayStation controller would be better).

That said, I haven't installed the iShock drivers for OS X at all, and it works fine with everything that supports pads via HID.

[MacmanX]

Originally posted by Wevah:
Their drivers, yes.

I still like the actual iShock controller better than any other USB controller I've used (though hooking up a real PlayStation controller would be better).

That said, I haven't installed the iShock drivers for OS X at all, and it works fine with everything that supports pads via HID.

Yeah, I was wondering if you needed the drivers for iShock. Most games let you customize right in the game. I'll have to try out my games sans driver.

Still, that was one crazy bug. Does anyone know exactly why the driver decided to write a multi-gig sys.log? I mean, that's a lot of saying "can not communicate" or whatever.

[kklenz]

Originally posted by Kenneth:
I ran the update on both of my Macs;
1) DP 1.25 PowerMac G4(FW800)
2) Original iBook 300

I repaired permission on both Macs before running the Software Update. So far, I didn't notice any problem on eating up RAM and storage space.

I'm new to this so "repair permission" means typing your user name and password first before upgrading software? If not, is there any documentation showing how to do this? Thanks.

[CharlesS]

Originally posted by kklenz:
I'm new to this so "repair permission" means typing your user name and password first before upgrading software? If not, is there any documentation showing how to do this? Thanks.

You don't need to repair permissions before running Software Update. It's a waste of time.

[Hi I'm Ben]

Repairing premissions as an answer to fix 90% of peoples problems is also a waste of time.

It seems like these days If I made a topic that said "My monitor won't work"

First guy would say "Try repairing premissions"
the next would defintely chime in "Run Software Update"

[CharlesS]

Originally posted by Hi I'm Ben:
Repairing premissions as an answer to fix 90% of peoples problems is also a waste of time.

It seems like these days If I made a topic that said "My monitor won't work"

First guy would say "Try repairing premissions"
the next would defintely chime in "Run Software Update"

"My computer turned off because we have a power outage"

"Repair Permissions"

"My keyboard won't work because I spilled a quart of my special vodka-Mr. Pibb combo on it and then somehow managed to plug it into the VGA port"

"Repair Permissions"

"My computer set on fire, exploded, and spewed burning shrapnel all over the room"

"Repair Permissions"