I recently installed Idea IntelliJ 10.0.3 on my Mac Snow Leopard. Whenever I try opening a project, IntelliJ starts indexing and in the process crashes!! It happens everytime.
I have Java 1.6.0_15 on my machine. I am not sure if this happens due to specific version of Java or due to a problem with my settings on IntelliJ.
Anybody experienced this before? Any fixes?
JDK 1.6.0_15 is known to crash because of GC bug, installing Apple Java Update is known to resolve this problem (current version is 1.6.0_26). Hardware problem mentioned by #xbit is also possible, but less likely.
I had this issue as well. It turned out to be bad memory in my case. Run Memtest if you are experiencing frequent crashes. Turn computer off, then hold down Command-S while turning on. This will boot you to single user mode. Then run "memtest all 2".
Related
Although I know that this Xcode version is quite old, my company's project still needs to use it and I didn't manage to make it ran properly on my company's mac.
Does anyone have faced this issue as well? Any idea would be very helpful!
ps. On my personal mac, with macOS High Sierra 10.13.1 Beta (17B25c), every time that I try to open Xcode 7.3.1, it crashes and doesn't even inform the reason.
It works on my machine... I know that doesn't help you but I just installed it and it opens ok. Maybe upgrade to full version?
After running Xcode 7.3.1 on MacOS High Sierra 10.13 VM, I can confirm that I can compile and run build on Simulator and devices with iOS6 & iOS7.
Unfortunately, there is no Cross-Compability-Guide to downgrade to older Development Environment or generell Software on newer Mac, because only minimum Requirements are listed in wikis like this:
https://de.wikipedia.org/wiki/Xcode
So, my tip on this topic is really to use older Hardware to test on matching Environments or try Virtualisation such as Parallels, Fusion or Virtualbox.There are differents in Virtualisation too. If some Virtualisation fails e.g. Virtualbox, maybe another Program (e.v. Parallels) does the job well.
I really use older Mac Hardware for testing older Software-Versions and that is the best tip I can give you on this topic. So its a good idea to have an older Hardware Repository to do this jobs, on which virtualization fails.
I know some Apple Developer which use some older Mac minis in their basement - remote connected - to solve problems like this.
I have an extremely annoying problem!
Xcode 7 crashes almost on every breakpoint when it tries to symbolicate.
I have done several things including deleting Xcode and reinstalling it...
I also had the same issue on the previous Xcode 6.X
Any clue? I am wondering if I should reinstall mac OS from scratch...
I solved the issue by changing the optimization level in the build settings, make sure it is set to None for Debug configuration and make sure your RUN scheme uses Debug configuration.
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!
i'm developing iPhone apps. Yesterday i updated leopard to snow leopard. Alongside i made the jump from XCode 3.1.4 to 3.2.4
I was always quite happy with XCode - working most of the time under windows, I really appreciate how well the XCode toolchain works together.
however - i'm not happy with 3.2.4 at all. i experience a lot of flaws, mainly with debugging. When an error arises, the debugger often stops at another place than the actual error happened. Sometimes the debugger does not trap into breakpoints at all and i get after some time a Error from Debugger: mi_cmd_stack_list_frames: Not enough frames in stack - whatever that means. And also I get invisible breakpoints which i can't remove anymore.
Does anyone experience similar things with XCode 3.2.4? if so, which is the newest release that works well?
Thanks!
Usually the problem is to do with level of debug symbols or some compiler optimization (which shouldn't be applied in debug builds). Maybe the information here will help.
Also try a complete clean (delete the build folder, remove the app from the device/simulator) & rebuild. Ensure you're working with the Debug configuration.
i have snow leopard 10.6.3 installed via iAtkos..everything runs good even XCode as well.I can successfully build iPhone apps run them on the simulator and the device but when i use the "build and archive" option( for adhoc distribution or itunes connect ) XCode simply crashes..does anybody have a solution for this?
thanks in advance
btw XCode version 3.2.3(tried 3.2.3 as well same result,also in safe mode)
Mac OS X version 10.6.3
I had the exact same problem, and it turned out it was caused by a variable of wrong type in info.plist. My short bundle version was created as int instead of string.
I was getting the warnings about it, but it didn't seem relevant since the crash happened only when archiving, and normal building worked fine, the app ran fine. I suggest you check your benign looking warnings, one of them could fix the issue.
You might try 3.2.4 (available now).