Every time I open my app in Xcode 4.4 it crashes. It never used to do this in Lion and being very close to submission after about 6 months of work, I'm pretty annoyed to say the least!
This is part of the crash report if it helps; I can't make head nor tail of it. If anybody can help me, I'd be forever in your debt.
UNCAUGHT EXCEPTION (NSBadBitmapParametersException): Overflow allocating bitmap backing store. Cannot back bitmap with 1152921504606846976 bytes per row, -9223372036854775808 height, and 1 planes.
Um, have had that issue what I did Is delated xcode and redownloaded it.
Hope that works!
Experiencing such kind of problems, I got the following conclusion: 3 files can be corrupted
Your project file, in that case try using time machine to get the
one which will work
The XCode prefs: /Users/xample/Library/Preferences/com.apple.dt.Xcode.plist
Your project's Derived data ~/Library/Developer/Xcode/DerivedData
If one of those is corrupted, it will corrupt the 2 other one. To recover a project, start trashing the pref and derived data, then try to open your project. Reinstalling XCode did not solved my problem, using the DP4.5 neither in my case.
HOWEVER: Installing the latest "Command Line Tools for Xcode solved it (and this is probably the first thing to try)
Sounds weird but Xcode 4.4 has problem with printing out logs of big strings.
I had the same problem, and I deleted an NSLog which printed a big amount of text, and the crash stopped...
For me, I'm getting this crash when trying to open a particular .storyboard file from the project view. If I open the file directly through finder, it doesn't immediately crash so long as the window is small. If I try to resize it or scroll one of the views into view, it will crash again.
I faced same issue with XCode 4.5.1. It keep crashing whenever i open storyboard and it throws following error:
Application Specific Information:
ProductBuildVersion: 4G1004
UNCAUGHT EXCEPTION (NSBadBitmapParametersException): Overflow allocating bitmap backing store. Cannot back bitmap with 1152921504606846976 bytes per row, -9223372036854775808 height, and 1 planes.
Apple released new developer preview version of XCode 4.5.2 last week, which has fix for all intermediate crashes that we saw in previous versions. This build is available in https://developer.apple.com/devcenter/ios/index.action
You can try this.
This is going to Apple as a bug report I'm afraid; they said from the crash report that it looks like a bug. Thanks to everyone for their help.
Related
I can no longer access any storyboards or XIBs in my project. As soon as I do,Xcode starts building and when it gets to Signing product it just hangs. I left it open for about half an hour, nothing happens. I need to Force Quit every time.
Signing works otherwise thou, that's the weird part. I can build normally, I can run on simulator, device, I can archive, everything is fine, EXCEPT when I open an IB file.
I tried all the usual, deleting DerivedData, cleaning everything, nothing seems to work. This is extremely frustrating and I can't find anything on the subject.
I'm using Xcode 8.2 beta (8C30a) currently, but it's also happening in the release 8.1.
Can you file a bug report with a bit more info? Please provide a copy of the build log and the output of sysdiagnose Xcode (it will produce an archive).
http://bugreporter.apple.com/
Thanks!
I set the constraints of layout properly and also tested it on every device. But the next time I open the project, Xcode just ruined the constraints totally.
How did this happen?
May be the project has a problem and for some reason it is not saving the changes. I have indeed put this solution on my troubleshooting book about Xcode from Apress (shameless advertising... 😃). I have seen this before.
Backup your project and try this:
Quit Xcode
Using finder, right click on the .xcodeproj file of your project and select Show Package Contents.
delete everything from that except the file project.pbxproj.
open the project again fix the constraints and see if the changes are saved the next time you open Xcode.
You did not specify you Xcode version, but my own experiences with code, that is developed using Xcode 8 Beta 1 to Beta 6: The problem may be caused by bug in XCode.
The explanation, if you use Xcode 8 Beta, could be:
New Xcode offers new storyboard-display logic, that shows different difficulties still in Beta 6
After fixing both constraints and frames automatically / manually, warnings come back again after reopening project
This problem moves from Xcode Beta 2 to Beta 6 after my own researches
Let's give Apple a little more time to fix the issues and let's wait until Apple releases GM Seed. It's only beta though
I recently upgraded to Xcode 7.3. I found that loading up the storyboard can take anywhere from 5 to 10 minutes to complete(and may sometimes result in a crash). I've restarted my Mac several times. I uninstalled Xcode and reinstalled it to no avail. I then cleared my Derived Data as well as com.apple.dt.Xcode to find that this did not help either. Is anyone experiencing a similar issue and possibly has a solution?
Although this actually might be an issue with incremental changes in Storyboards with Xcode 7.3 you can always speed up build times by creating multiple small Storyboard files in favor of a big bloated Storyboard.
Xcode can then reuse already built Storyboards in subsequent builds (as long as they are not changed) instead of building the complete bloated Storyboard over and over again even for small changes.
Apple even has a guide that might help getting this started.
I hope that helps!
This is really annoying bug/issue with XCode 7.3. So, If you have an hour or so to spend you can download and install XCode 7.3.1 Beta from here https://developer.apple.com/xcode/download/
It seems that this issue has been fixed in this version (at least it works for me).
Edit: OK. After a few minutes, Interface Builder became extremely slow again. Changing only one property can take up to 15-20 minutes.
After some research I have figured out that autolayout constraints were the cause of this issue, BUT only if you have a combination of some components present. I had a segmented control inside a navigation bar. When I removed navigation bar and placed segmented control in a simple UIView, all issues were gone and IB was smooth again.
Hope this will help.
I am using Xcode 7.3.1 and had the same problem. My problem was solved by disabling source control.
Go to Xcode->Preferences->Source Control and then Uncheck the Enable Source Control. Worked for me.
Thanks.
Sometimes the storyboard gets slow because of unresolved errors of autolayout. In my case i tested by changing screensizes and it showed me some errors on different sizes. Once i resolved those errors the storyboard was working fine. Please confirm
Yep I had the same problem. In design mode, it's Autolayout that is causing the 5-10 second delay between edits, especially if it's a large storyboard. Turning off Autolayout in the storyboard at design time fixed the issue for me:
Open project
Select storyboard from the Project Navigator
Open the file inspector
Under Interface Builder Document uncheck 'Use Autolayout'
If you need Autolayout at run time, I recommend you layout your Storyboard in design time with this off (to avoid those long delays between edits) then turn it back on afterwards. Or, turn Auto layout on programatically. Or better yet, split your storyboard out into smaller storyboards.
Referenced this question: Can I disable autolayout for a specific subview at runtime?
I got the same issue recently after I updated the OSX to 10.11. Xcode 7.3 will take almost 5 mintues to respond when I just change the button's font (or anything else change). This made me almost crazy. Incidently, just for a try, I updated Xcode from App Store to 7.3.1. Then I was happy to cry when I opened the storyboard and changed the attributes. Xcode responds smoothly.
So please try Xcode 7.3.1 for your problem. Hopefully you can be happy with it.
I'm experiencing a very strange error: my Xcode is freezing when I quit a certain storyboard of a certain project.
When i open Xcode, the xib shows up normally, I can even edit it and save it. But when I'm trying to open another file, any other file, it freezes forever.
I tried to delete every temporary files as described here, or here, or here, but the problem still remains. Ah, and... re-create my xib is obviously not an option...
Any other idea?
EDIT:
When I delete myProject/[project.xcworkspace/]xcuserdata (s), I can navigate in my project as usual while I don't open the storyboard. otherwise my problem comes again.
Since my post about this problem, I saw it on other projects. I'm pretty sure this was linked to custom fonts in xib, because it often happened after an Xcode bug rendering custom fonts.
Few days ago I downloaded the last Xcode version, 6.3.2, and the problem did not bother me again. So it seems to be resolved.
I can't load my MainMenu.nib file to my application in XCode. The console log reveals nothing and I'm hoping my .nib file is not corrupted somehow. Please Help!
3/2/12 10:39:29.134 PM Xcode: Exception raised while
decoding document objects -
*** -[__NSArrayM insertObject:atIndex:]:
object cannot be nil
It has happened for me, too, after upgrading to Xcode 4.3 some of my .nibs refuse to open.
I filed a bug to Apple a couple of days ago, but still no answer.
Upgraded just now to Xcode 4.3.1, the problems are still there:
The document "***.nib" could not be opened. The operation couldn’t be completed. *** -[__NSArrayM insertObject:atIndex:]: object cannot be nil.
As a last resort I'll try to downgrade to Xcode 4.2.
I have tried to open these nibs in a text editor (they are just xml, after all) and they open regularly. They appears intact and healthy. The problem is all in Xcode and it is over my possibilities.
Paolo
Have you tried deleting the ViewController of the nib file together with the nib file and recreate them? There's a couple of way to go around it. Had the same issue and recreated my ViewController without nib file. Then add the content programmatically. Taxing but with more control and flexibility.
Downgrading to 4.2 will prohibit chances to test your app on your device running 5.0.1 (if you have upgraded those devices.