Asking this on SO as well as the Unity network, hoping someone can give me a hand.. I'm running into an issue that seems to be specific to 4.6.x versions of Unity. First, the specs: I'm running a Mac Mini with an i7 Processor, 8GB of ram and OS X Yosemite.
Now, I've been able to run Unity 5.x without any issues (This is my last resort, If I have to I'll end up running Unity 5.x, but I'd rather run 4.6.x), but when I attempt to run any Unity 4.6.x version, the editor application itself attempts to start up, and immediately crashes. I've attempted uninstalling & removing preferences, rebooting, different versions, etc to no avail. Has anyone run into this issue before, if so what was the fix? I've heard that this was a known issue at one point, but was fixed in Unity 4.6.1 (which I've attempted to run unsuccessfully...)
Thanks!
Related
Is there a version of MeshLab that supports MacOS 10.11.6? I have tried to use MeshLab2021.10 for the first time tonight, and when I try to launch the app it crashes immediately. I realize that 10.11.6 is an older system but I am on a fixed income and cannot afford to replace my computer at this time.
I tried finding a version of Meshlab that would run on my computer by starting with the newest version and, upon seeing it grayed out by my OS, finding the next-oldest version & repeat until one was not grayed out. Nonetheless it crashes immediately when trying to launch it.
All I've done is unpack the zip, and when I try to open Android Studio, it crashes immediately. I see the icon in the dock for two seconds tops, before it crashes.
I also tried using the latest Canary build and have the same results.
I checked and apparently JDK comes bundled with it, so I don't need that installed in advance.
Am definitely using the M1 / ARM build for macOS running macOS Monterey Beta.
The traceback error is incredibly long and I am unable to pin where the issue lies, and I'm not sure that I should really post the entire thing. Where I am confused is that this is a relatively new Macbook Air on the M1 chip with hardly anything installed on it, so I don't understand what the conflict is or where to begin here...
Fixed by upgrading to the latest beta.
Appcelerator Studio, build: 4.7.1.201609100950
macOS Sierra 10.12
iMac (Retina 4K, 21.5-inch, Late 2015)
Java 8
Node.js 4.4.7
npm 2.15.8
Titanium CLI 5.0.9
I've tried (many times) to reinstall the editor, but without solving the problem. The editor is really really slow when scroll (after macOS Sierra update). It's impossible to use it without going crazy. I use Appcelerator Studio for many years and i have never had these problems.
There are other external components that could upgrade / reinstall? (Java.. etc etc)
Thanks
Update
In addition to the slowdown, the editor does not properly recognize the file format.
I had this slow down issue with appcelerator Studio as well (some of my colleagues swear by using Atom editor)... this happens with Appcelerator when you have one .js file that is huge (thousands of lines).
Ideally, split your js file into seperate commonJS files and coll them into the original js file with require('filejs')
I also had this problem for almost 1 month and I went completely crazy one day due to Studio slow-ness.
I tried complete fresh installation of Appc & all of its components 2-3 times, but no luck.
Then on one day, it was not working even like previous day, so I decided to completely format my MacintoshHD and re-install the macOS Sierra because I noticed that some other normal apps like Skype & Email were also started working slowly. So I got the idea that it's related to macOS Sierra update.
Very Important Note (take system backup first)
Before installing OS, I took backup in external hard-drive and then I ran the First Aid (Disk Utility Tool) on MacintoshHD and found that there were some corruptions in it, so I fixed them but then something really crazy & out of this world happened with my system - Kernel Panic and my system did not start-up for 3 hours of hectic try.
So the last solution was to format the Macintosh HD & install the OS again. The best way to do this is to make a bootable pen-drive having macOS Sierra in it and then install using it.
Another way (if you have very good speed LAN) is to connect your system to Apple server and let it install latest OS from online. But it will download the whole OS & other required files (of at least 5GB size).
There are many online tutorials on how to install macOS Sierra again after such creepy issues.
FYI: I did re-installation of macOS Sierra last week & now everything is working like it is supposed to work on a Mac machine (just buttery smooth.).
After updating OSX and Xcode to latest versions (10.8.4 | 4.6.3) projects with cocos2d 2.0 works fine but...
When I tryed update cocos2d to 2.1 new projects want not build. Xcode just closes with error.
Full error description here: https://docs.google.com/document/d/1JhqD3CW2JRKEXZquQIYN4grVG3siDL4jqcFByhGDgGM
After this error projects with c2d 2.0 that works before starts crashes too.
Back cocos to v2.0 does not give any profit.
Problem resolved.
I use RealVNC server on my home mac and client on win7 PC at work.
Xcode crashes when I try build/run using shortcuts (command+R, command+B, sometimes command+z)
When I do this using menu, it works fine.
Weird, why this starts after cocos2d 2.1 installed...
So, I think, problem with OSX 10.8.4 + RealVNC.
Weird weird weird...
Directly Mac works fine.
P.S. I hope this will be helpful for another internet pilgrims.
My Xcode 3.2.6 is hanging up constantly.
While I'm coding with no apparent reason it starts consuming more and more CPU, CPU temperature rises up to 80 celsius, the fan get exhausted and I'm forced to "force-quit" it and relaunch it to be able to continue working...
It start happening this week and nobody else on my project is having the same troubles.
My OS is Snow leopard 10.6.8
Any ideas on what could be happening?
I had the same exact issue with my Xcode 3.2.6 project... Would start out using one core and if I let it sit, would use all 8 cores of my i7 MBP. Very frustrating having to restart Xcode every 5 minutes.
My issue actually was resolved when I removed an iPhone from the Organizer that was running iOS 5.0.1. Xcode was trying to get information from the iPhone, and wasn't able to, since the iOS SDK requires Xcode 4.x
I also removed all the user settings from within the project's *.xcodeproj package as well; not sure if that had additional effect. removing those without removing the iPhone had no effect, though.
Have you tried doing a "clean" on the target? Have you tried checking your disk with Disk Utility?