Mountain Lion freezing

ML is doing strange things to 1Passport, etc.

I sent the screenshot to Agile and they replied -

I've not personally seen this before, but I believe it is a known problem with Mountain Lion. Please read the below link which has a workaround 🙂

http://support.agilebits.com/kb/1password-39-for-mac-from-mac-app-store/hiding-1 password-enables-secure-input-mode-which-may-affect-textexpander-typinator-and-d ictation-in-mountain-lion

Thats silly. Why leave 1Password open? Just quit it.

And it sounds like 1Password caused this problem by getting carried away with "security".

Try RoboForm sometime.

I think I will comment on this thread whenever ML forces me to do a hard shut down. Can't wait for .3.

I also had this problem before with my computer freezing in ML 10.8.2.

The thing I did was ran Onyx and under the Automation tab I had all the stuff checked and then I press execute.
After that the computer rebooted and I started to use Chrome and not Safari. Because in Safari my computer was unstable. Safari frooze up and the kernel_task went up to 100% and I couldn't reboot my computer.

I'm not sure what is causing this issue but now my 10.8.2 is stable when I don't use Safari and I had ran Onyx. I did never before a re-install of the operating system.

I have the same problem with my late 2009 MP: ML freezes, it's still possible to move cursor, but the system doesn't respond on anything else. The only solution is to restart the computer. I have installed ML also on my 2010 iMac i7, and I have absolutely no problems here. I have performed a clean install on the MP, did not help. I tried to isolate the problem, I installed only software that I purchased from the Apple Store, such as FCPx, Motion and Aperture. These programs doesn't seem to be the problem. In a further test I thought to isolate the problem due to a problem with iTunes as it was always playing one particular album when it frooze. I deleted the album, but tonight it frooze again. The only third party driver that I have installed is for my Wacom Pen and Touch Bamboo Tablet. For now I have disconnected the tablet (it was always attached as the system freezed); now I wait what happens.

This is a realy frustrating problem as I can see the potential of ML on my working iMac (I upgraded from SL). I hope Apple will solve this problem asap.

Monday the first Beta of 10.8.3 was seeded. As Apple requested specific testing of the Graphics Drivers, they might perhaps even have been working on this issue! Imagine... 😝

Let's try it one more time... Safart open, screen freeze, hard shut down.

I'm getting freezes with the ReportGPURestart message. They're pretty specific: If I open Minecraft, enter a world, and try to toggle fullscreen on or off, I am very likely to get such a crash, and if I was fullscreen, the last frame shown just stays up forever, even if other programs start and think they are displaying graphics to the screen. If I toggle fullscreen only from the settings screen while not in the game world, it seems to work fine.

MBP (classic) June 2012, 15", using an external display (so it's permanently using discrete graphics). Current minecraft, same behavior with both Java 6 and Java 7 runtimes, have updated the lightweight java game library and other bits, no change at all in behavior.

Nothing else seems to cause any problems, apple hardware test reports nothing. So basically, there exists something that Java OpenGL games can do which causes the GPU to crash, and the crash recovery is defective.

I was also having same problem (mainly safari crash, freezing issues) from last week . I tried everything reinstall , diskutility repair permissions , ody software, drivers update and lot of things i could find . Finally what worked for me, anyone especially User using Bootcamp (can be a possible cause), i will suggest u to try this . hope it will work for u.

boot into single-user mode (Command+s). Once you see the spew of white text on the black background, you can release the keys. Eventually you will arrive at the root ‘#’ prompt. Do the following for low-level disk repair, write the changes to root partition, and reboot.

# fsck -fy

# umount -uw /

# reboot

Now you leave the Console open waiting for a hang or more mischief. Hopefully, it will be gone.

ekhadka,

You recommend this:

# fsck -fy

# umount -uw /

# reboot

What does this root-level partition change DO? Are you eliminating the soft partition or what?

I understand why you would repair the disk at the root level and run dsik utility, Onyx, AppleJack, and/or similar

utilities at that level, but I don't understand the coding you suggest well enough to know what you are up to...

Thanks,

Jon

mid-2009 MBPro 2.26 GHZ, now on Snow Leopard 10.6.8...

(and tempted to stay there...)

"fsck -yf" is just "run a filesystem check, fix anything that looks like it needs fixing". It's not functionally different from running Disk Utility's "repair volume".

This is not coding, just entering commands. The reason it's done single-user is so you can check the disk without other programs interacting with the disk -- you can't do that to your boot drive from disk utility. This is basically the same as booting to recovery and running repair volume from there.

It... well, I would definitely not expect it to change anything, since the mac will run fsck during boot anyway and Do Something if it thinks there are problems.

Seems like Safari is always open when the freeze happens.

Yeah, I seriously think it is an Safari-issue. Stop using Safari! I'm using Chrome and it is fine

But SOMETIMES everything freezes because I have an "e-learning platform" open which I study to get an ISTQB-exam. Maybe it is the homepage that is making everything crash but I'm still on Chrome when it happens. When I don't use the e-learning platform nothing freezes. So I think you don't need to worry 🙂

I still have intermittent freezes (though I can't ever find a common element) and rarely use Safari. I primarily use Chrome.

Likewise, I wiped (zero out) my HD and reinstalled OSX 10.8.2 and my programs and it's working without a issue.

I have a feeling that the upgrade path used to move from Lion to ML wasn't able to handle all the variations in hardware and software of apple users.