Search Issue Tracker
Fixed in Unity 4.3.4
Votes
241
Found in
4.2.2f1
Issue ID
571984
Regression
No
Maverick and Unity performance issues
On some Mac's with OS X 10.9 Unity performance is very bad, including stuttering, editor freezes, editor lags and similar.
We found that there seems to be a leak in Maverick's OpenGL ARB VBO implementation.
Our text rendering creates and destroys a lot of VBO's so it is most likely that this happened after around 10 minutes of working with Unity and the inspector or other text heavy components in unity uploading a lot of geometry.
Terrains will be especially affected, but of course just loading a scene / unloading a scene will load / unload VBO's for all the meshes too.
This issue has been fixed with a workaround in 4.3.4. We are working with Apple to get a proper fix done, at which point we will be able to remove the workaround.
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- One Input axis does not work after using Input.ResetInputAxes() while both axes are held down
- [UWP] Build fails when the project folder name has non-ascii character.
- Prefab Asset changes are not reflected inside Prefab Editor when Unity Editor is in the Play Mode
- [Audio] DSP Buffer Size sets to Best performance when pressing trying to set to default
- [LWRP][VR][Android] Cardboard VR: Extreme incorrect distortion on some Android devices
pneill
Dec 08, 2013 16:01
Anyone know if there is a chance this will get fixed before the holiday? This is so frustrating. This normally the most productive time of the year for me, but this issue is killing my productivity. It's barely usable. At minimum, I hope that Unity Test team will develop a new test case to cover this issue for future releases. This is a show stopping bug and worthy of hot fix.
RyanZimmerman87
Dec 06, 2013 06:06
This bug appears to be fixed in 4.3.1 on Late 2013 Macbook Pro. My biggest problem of Monodevelop being sluggish or having momentary lag spikes seems to be fixed.
Everything has been smooth sailing so far today after about 5 hours of work. A little early to say it's gone for sure but it seems that the "Deadlock" thing from the patch notes fixed this for me.
A bit worrying others are still having problems, but from what I see so far it's enough to remove my vote for this issue.
Unity still freezes for me when I close MonoDevelop before closing Unity in Windows 7 which I suspect is related to DirectX 11 which I recently enabled, unrelated but I guess I'm gonna have to look to see if that's a reported issue yet...
pdwarne
Dec 05, 2013 16:01
still getting this in 4.3.1 on an early 2011 MacBook pro. (friend has 2012 macbook pro with no issues). Unplugging the second monitor does appear to help fractionally. Approximately same frequency of freezes but they each seem to last for shorter periods- but remains an unworkable condition to develop in and it has been a week now.
zbyhoo
Dec 05, 2013 09:44
This bug is frustrating as hell.
For me Unity start to work better when I disconnected my external monitor from my macbook pro.
Messu Kilkain
Dec 04, 2013 12:01
I just wanted to highlight something : the bug is registered for Unity version 4.2.x but I'm working with Unity 4.3 and it still freeze sometimes/often.
The worst thing was I was forced to upgrade to Maverick for building for iOS 7, then I realized that it was freezing and then I updated Unity but it still laggy.
RyanZimmerman87
Dec 04, 2013 03:03
Edit: MAJOR SLOWDOWN COMPARED TO PC!
Seems like it has gotten worst the last 2 days for some reason... even just coding in Monodevelop seems a bit choppy and unresponsive. If it's this bad on the Late 2013 Macbook Pro it must be a nightmare on the older models.
I'm about to switch back to PC for my work if this keeps up. Been trying to get used to working efficiently on the laptop but I can't stand getting this kind of lag even when the games not even running. Monodevelop should not lag AT ALL what the heck is going on here?!
RyanZimmerman87
Dec 04, 2013 00:10
Have noticed a bit of a slowdown on Late 2013 Macbook Pro compared to my PC. Then again my PC is Intel i7 over clocked @ 4.3 GHZ with a 770 gtx graphics card.
So I thought the Macbook being a bit slower was normal, but that's great if it's a real issue and can be improved.
Snupiman
Dec 03, 2013 15:52
Ok I think I have annoyed quite a few ppl because I have now received an email from unity saying this:
"Thanks for contacting support. We are aware of the problems with Mavericks and our team is currently working on it. It is of high priority given that it is affecting users a lot."
This makes me a lot more relaxed now. Hope that they stand to their words and fix it soon!
Zincoontrin
Dec 03, 2013 14:10
You are not an angry developer. It's the sad state of Unity, in my opinion. I still remember the first time I saw Unity in 2007, when there even wasn't a windows version. It was heaven. That's when their slogan "Taking the pain out of game development" held true. Not today, certainly.
But... David Helgason went to San Francisco, the company got VC money and everything got crazy, development-wise.
I propose everybody tweeting to @davidhelgason to express our sorrow.
Snupiman
Dec 03, 2013 09:31
OK I have written an official email to Unity. I am licensed Unity Pro user but despite that I have heard nothing from anybody. This issue should be taken seriously by now! Ill certainly not finish my game before christmas due to this freezing issue and this my friends will shine really bad light on Unity. Its imposible to work like this! Maybe I'm one angry developer but clearly I'm not the only one. It is possible that someone in Unity has a weird fetish for collecting angry indies! I SAY FIRE HIM/HER!!!