Setback (Update)
A month or so ago, after the most recent OS X update (10.8.2), we’ve bumped into a problem that causes certain Macs to restart when intensively using Pixelmator. Sometimes, the app would stop responding without restarting a computer, or just cause some graphical glitches.
We did everything to find the root cause of the problem. We’ve researched a vast amount of information about OS X internals. We’ve torn down our Macs. We even reached out to Apple. Finally, the picture was clear: It’s an issue with NVIDIA GeForce graphics card drivers.*
Although the issue isn’t with Pixelmator, we didn’t give up. We’ve searched for various workarounds, and then, we checked with you to see if any of them helped (thanks so much for being so patient and for taking the time to test those workarounds). But in the end, nothing worked.
Good thing, though—the guys at Apple are very helpful, and as soon as we hear about a solution, we’ll let you know about it that very moment.
To prove our commitment to you and to brighten up the holiday spirit, we are soon to release a Pixelmator 2.1.4 update that comes with tons of quality improvements.
* The following Macs with NVIDIA GeForce graphics cards are currently affected: GT 120, GT 320M, GT 330M, 9400M, and GT 9600.
Go ahead, everyone, and download the OS X 10.8.3 update to your Macs!
I suspected this was part of the reason Apple ran through so many betas asking people to test out graphics drivers. Whatever the case may be, I want to thank you guys (in addition to Apple and Nvidia) for getting it together and making sure that your product remained one of the best-supported and inventive applications available for OSX. Great work, guys.
I am afraid that for me Pixelmator 2.1.4 crahes every time on launching under OS 10.8.3. No other issues with the OS update.
Mac Mini i7 2.7 GHz, AMD Radeon HD 6630M Graphics card. Reports sent to Apple.
Hope the excellent Pixelmator can be resurrected,
@Warren Hill, email us the crash report to bugs@pixelmator.com. We’ll take it from there.
[...] som för övrigt är på gång med en ny version, har ett tag dragits med ett problem som gjort att appen låst sig. Problemet har dock inte varit Pixelmator:s fel utan legat i [...]
[...] appears that the issue has now been resolved with the release of OS X 10.8.3 last week. From Pixelmator’s blog: Since the release of the OS X 10.8.3 update last Thursday, we’ve been thoroughly testing [...]
Yeah! never experienced this issue but i’m happy for Pixelmator and its users.
I had Warrens problem too. It was more pervasive though. I upgraded to 10.8.3, and anytime I launched non-apple software (from pixelmator to StarCraft2), I was logged out. When I logged back in I’d start over. My eventual fix was:
1) Decrypt my HD (I was using FileVault)
2) In Disk Utility, repair the disk
3) There was no step three…
I’m going to turn FileVault back on this weekend. At this time, everything is working.
[...] has been released, Pixelmator has announced that the restarting bug has been resolved. From a blog posting on their [...]
[...] has been released, Pixelmator has announced that the restarting bug has been resolved. From a blog posting on their [...]
[...] has been released, Pixelmator has announced that the restarting bug has been resolved. From a blog posting on their [...]
Seems to be a bug with the CSS on this page which makes the text unreadably dark on iPad. I’m still using iOS51.1. Thought you’d like to know.
Well I’m still kind of scared to try it. But I guess I will. MacBook Pro 15 in. OS X 10.8.2, NVIDIA GeForce 9400M 256 MB. I really hope it is fixed.
I’ts a great news at last. Congrats
This is great!
I have used PM for a while and NOW like the rest of its users are tired of having to forcequit the program and restart our comps. So FIX THE PROBLEM!!!! Why would I continue to use a product (That I unfortunately paid for) when there are others that might be more money but at least they do what they say they do. My comp is a iMac with only .25 memory and less then that used in RAM and all updated including pixelmator but still even with the COUNTLESS promises with NO results we continue to follow like sheep. NO MORE. Fix your program or stop selling!
4
The text on this page is so dark its barely readable. have to turn up the brightness to 90% on my 23″ cinema display.
[...] appears that the issue has now been resolved with the release of OS X 10.8.3 last week. From Pixelmator’s blog: Since the release of the OS X 10.8.3 update last Thursday, we’ve been thoroughly testing [...]
Hmm, just some minutes ago my Mac restarted itself while using Pixelmator. That is using 10.8.3. So unfortunately I have to report that the problem isn’t entirely solved, but at least it happens less often than with 10.8.2…
@lemon-kun, could you email us the crash report? We’d be able to check whether it is the same problem.
@Nathan, the problem is not with Pixelmator, did you not read the top of this blog? Please, give these guys a break, besides how much did you pay for pixelmator, 15 bucks. Good grief, your a baby.
I have an iMac with NVIDIA GT120 and, although the issue was apparently solved once I installed 10.8.3 update, after several days using it I started to have system crashes again. So I think the problem has not been resolved yet at all. People in Apple’s forums are commenting the same.
I know this is not a Pixelmator issue, but I’m sure that the Pixelmator’s team help on having Apple working on this issue can be a great assistance for so many frustrated Apple+Pixelmator users.