Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
it might be that this issue is related to iphone syncing, as some other posts in the macrumors forum suggest. can you try if your machine crashes without iphone syncing under heavy load?

The iPhone synching was syncing photos and chewing up full CPU load on 4 cores. I recreated the lockup running just yes > /dev/null remotely via ssh, so its definitely not just an iTunes/USB thing.
 
There is no harder/easier between DirectX and OpenGL on OS X.

OpenGL on OS X is NOT A DRIVER ONLY DESIGN.

OpenGL on OS X is accelerated within the entire WindowServer and thus via Quartz Extreme all object primitives/window views, etc., are OpenGL accelerated at the same version of the OpenGL Driver.

OpenGL system-wide acceleration is 2.1 for OS X 10.5.

OpenGL system-wide acceleration for OS X 10.6 is nearly 3.x compliant.

Apple is moving to OpenGL 3.x system-wide. [3.1->3.3]

To put this into perspective:

Windows DirectX 11 is not system-wide even on Windows 7 [it's actually DirectX 9.0 for it's Desktop Windows Manager], but only at the device driver level leaving it to the application to leverage DirectX 11 or earlier, down to DirectX 9.0 in Windows 7.

Linux OpenGL Desktop Environments are all OpenGL accelerated at 1.4. Sure, I have OpenGL 4.1 device drivers but the Window Server [Xorg] is pushing out at 1.4.

KDE/Gnome are moving to OpenGL 2.x [actually OpenGL ES 2.0 being a subset] in future versions of KDE/GNOME.

OS X must fall back to OpenGL 2.1 if a GPU doesn't have 3.x support. The same will be true when OS X is OpenGL 4.x accelerated by falling back to the next lowest OpenGL revision supported.

Testing OpenGL system-wide takes a helluva lot more work than writing an OpenGL Device Driver and leaving it up to each app vendor to leverage OpenGL directly via their needs.

Apple making the entire system OpenGL ready means the 3rd party vendor's codeing footprint drops dramatically.

Now that Apple has the iOS Platform, its only expanded it's OpenGL footprint to this platform to design, develop and test with each revision of the OS.
Do you know if Apple allows the OGL to fall back to CPU when it encounters code that the hardware can't support?
 
Oh its even more funny when you repeat/steal another users comment.

I would say that "Obviously" you are incompetent with computers and fall into the Mac User category of Ex-Windows users who fell for every fishing scam and Virus trick out there. You most likely had no concept of computer maintenance.

I've been using Windows, Mac, and Linux for over 25 years and almost never had a problem.

There are incompetent USERS ....Not Computers

I agree with excape
Ah, yes: the old 'I-do-have-experience' so as to suggest source credibility.

Unfortunately for you, that trick didn't work.
 
Wow, definitely glad I stuck with my 2010 model and didn't upgrade.
Haha there should be a short-cut button for that statement but just have the year editable :)
Every time Apple comes out with a new computer then something goes (some terribly) wrong , we always have that option (the ones holding the older model of course) to say that statement ;)
 
Wow, definitely glad I stuck with my 2010 model and didn't upgrade.

I keep thinking about replacing my late 2007 model. Now this has me considering a refurb 2010 over the 2011. The 15" 2.2 is exactly what I was looking at in the 2011 models.
 
Haha there should be a short-cut button for that statement but just have the year editable :)
Every time Apple comes out with a new computer then something goes (some terribly) wrong , we always have that option (the ones holding the older model of course) to say that statement ;)

Ya, we figured we were safe.. again .. and fail, again :/

That and 7 hours of battery life? Suuuuuure heh </rant>
 
Sounds like a OpenGL issue to me. I had issues with it when applications don't use it correctly
 
Issues here. It's happened running handbrake and running Civ 5 under Steam. Seems to be triggered or happen coincidentally around when I switch Spaces (A couple of times it froze up in the middle of animating switching between spaces), but I suspect that's just some interaction with the switch from discrete to integrated graphics (or vice versa). It's frozen up around 6 times since I got my 17" 2.3GHz/8GB/512SSD last week. In all but one case the mouse cursor keeps moving. I seem to be able to ssh in (I didn't try it the first few freezes though).

For those who say they haven't seen it, there is a test using a compile with photobooth running that they've posted in the apple forums; every person who's tried it has had the problem.

Any chance this could be faulty RAM? I just ask as I had a similar problem on a Mac Pro that turned out to be a bad RAM module.
 
Wirelessly posted (Mozilla/5.0 (iPod; U; CPU iPhone OS 4_2_1 like Mac OS X; en-us) AppleWebKit/533.17.9 (KHTML, like Gecko) Version/5.0.2 Mobile/8C148 Safari/6533.18.5)

Jswoosh said:
I haven't any problems yet either for it freezing however I have noticed that while watching 1080p youtube videos my 13" i7 tends to have the fan running after the second or third one I watch.

OH NO SOMEBODY CALL STEVE JOBS! My MacBook aluminum model gets steaming hot while playing some games and I use fan control to make it turn max fans on really low. Oh it gets hotter if the room your in is warm too.
 
I just did a test with my Mac Pro (early 2009) and Macbook Pro (2011).
I started a RAW to JPEG batch conversion with Lightroom and played
a 1080p .MOV file with the VLC player.
The Mac Pro didn't have any problems with it.
The Macbook Pro (2,2Ghz, 8GB RAM) couldn't handle it...during playback the
video froze every couple of seconds.
That can't be right, can it?
 
I built my own PC 3 months ago (I do not do laptops for I get them for my job). It has not crashed or frozen even once. Obviously - no viruses (it's Windows 7)

COOL-STORY-BRO.jpg
 
Haha there should be a short-cut button for that statement but just have the year editable :)
Every time Apple comes out with a new computer then something goes (some terribly) wrong , we always have that option (the ones holding the older model of course) to say that statement ;)

Seriously lol

I'm glad I updated to the 2011 model. I've already done just about the most resource intensive tasks I'll be doing and haven't had any issues yet.

There are always some legit issues with any update. A large percentage are non issues though like the whole iP4 antenna thing.
 
Seriously lol

I'm glad I updated to the 2011 model. I've already done just about the most resource intensive tasks I'll be doing and haven't had any issues yet.

There are always some legit issues with any update. A large percentage are non issues though like the whole iP4 antenna thing.

Seems to me that if there is a real issue, Apple will work on it and fix it. This was actually quite a big update considering it was a all new processor, and the addition of Lightspeed along with other things. Not surprising there could be some follow-up work.
 
Every so often something happens. I'd still take a Mac over a hand-built hackjob Windoze box any day. Even one that's due a firmware fix.

You're quite lame. Adding a "z" to Windows. Let me tell you my friend, building a custom PC to your specification for way under the cost of your high end Mac is an experience you'll never be able to have. Even better, my PC can run a Virtual of Snow Leopard 100% flawlessly. I have the best of both worlds, with my own specifications, at a fraction of the cost you shelled out for a product that is consistently having problems time and time again as Apple's Q&A seems to be lowering its standards.

If this current issue that Apple is having with their Pro line was an issue in Windows as well, this whole flipping forum would be there first in line mocking Microsoft [or as you would spell it M$] and hailing Apple as god.
 
Any chance this could be faulty RAM? I just ask as I had a similar problem on a Mac Pro that turned out to be a bad RAM module.

If I read everything correctly, if the same user uses Boot Camp to run Windows 7, then the issues don't occur, so that wouldn't be faulty RAM then.
 
Doesn't pay to be an early adopter/beta tester. Hopefully they resolve this issue. I'm looking to upgrade my late 2009 MBP.
 
I have the 15" 2.2ghz i7. I have had no problems at all with it, but for kicks, I'll try one of the tests when I get home.

Even if I reproduce the issue, I'm not going to freak out about it. My daily use clearly doesn't bring up any issues, and it does sound like this is something that Apple will be able to fix with a software update.
 
You're quite lame. Adding a "z" to Windows. Let me tell you my friend, building a custom PC to your specification for way under the cost of your high end Mac is an experience you'll never be able to have.

Been there, done that, prior to 2006.

I even played with customizing Windoze.

http://customize.org/screenshots/23989

http://customize.org/LTD

Then I outgrew all that and bought a Mac.

Dont forget, a lot of us Mac users are former Windoze users. There's a reason we switched.
 
Surprised it hung; PRAM/NVRAM + SMC Reset Solved It...

I haven't had any real trouble w/ my 2011 MBP 15" 2.2Ghz... and I often run under moderate-to-heavy load (executing high transaction rate JEE apps across multiple VMs for debug + verification testing). So, when I tried the "yes > /dev/null" test documented on the mbp-freeze wiki, I was surprised it froze up the computer almost immediately!

I'm happy to report, though, that after resetting the NVRAM/PRAM and also the SMC - I'm able to run all 3 proposed recreate scenarios from the wiki, simultaneously, without issue.

Hopefully other people have as much luck as I did -- just wanted to post it, to put some glimmer of hope out there for those of you planning to run home and test your machines later today.

(Note: I don't believe this is fixing it for everyone, but it did great for me... and even though I never encountered the crash before under normal usage, I'm glad to know it's now not reproducible)
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.