I just upgraded to Xcode 8 and am effectively stonewalled when trying to do anything. Xcode is taking anywhere from ten seconds to five minutes to execute what i've done. I.e. taking 3 minutes to identify a syntax error, four minutes to run through a for loop in playground of just displaying elements of an array.
Has anyone else experienced this issue? If so, were you able to resolve it? I have tickets opened as a bug report but unsure of how long it will take to hear back.
I found someone with a similar issue here https://stackoverflow.com/a/39949491/6484248
which has seemed to have solved my issue as well.
In short, add a User-Defined Setting as:
SWIFT_WHOLE_MODULE_OPTIMIZATION = YES
My lag has been completely removed on this project, though I can't explain how it has helped.
Related
Quick overview: I develop Excel Macros for a firm. The Macros are used in a daily basis for more than 200 workers. These 200 workers connect the Local Machine to a common server (there actually 3 servers) and run the Macros from there.
Problem: Today in the morning some of these Macros (different Macros) starting crashing Excel with the tipical message "Excel has stopped working". These Macros (which I didn't update) run every day without a problem. Today, just like magic, they starting crashing for different lines of code which only common denominator is that they use a lot of resources.
Ex:
sh.UsedRange.Value = sh.UsedRange.Value (the UseRange is alcually a pretty small range)
Application.Calculate
wb.Sheet1.Move
I understand these are functions that take a lot of memory but still they have been working for months without a problem until today. I know this could be more like IT kind of problem but since I'm trying to solve this issue, I thought maybe one of you either had this problem before or know a possible cause (like a Windows update).
IT already reinstalled Excel in all the servers that we use for remote connection but the problem persists.
Any Idea?
Thanks a lot,
Ok, here is what happened in case you guys see this problem in the future:
Everything is Microsoft fault's. They launched an update to fix some Excel bugs and instead of fixing them, the server that automatic updated their versions, got really messed up. This updated was launched on Mar/14/2017 (2 days Ago).
I made some research and this sounded very weird to me. They launched an update to fix Excel 2010 bugs and now my Macros are breaking without changing the code? It had to be that and there it was.
Here's the Log:
https://support.microsoft.com/en-us/help/3178690/ms17-014-description-of-the-security-update-for-excel-2010-march-14-20
Just keep your head up if you have Automatic Updates on in your computer and see problems like these happening. In case you find that's the problem, just remove the update from your Excel.
Regards,
I am currently running into a similar issue with an Excel VB script utilizing the Today() function. The script freezes up and becomes unresponsive when the date is 03/17/17, but if I change the system date to 03/16/17, everything works great.
It appears that there were a number of Microsoft Office Updates on 03/16/17, so I am going to try and remove them one by one and see if that fixes the issue. I'm starting out with the Security Update for excel, KB3178690.
Update -- confirmed, removing Microsoft Security Update for Excel KB3178690 fixes the crashing issue related to the date function after 3/17/17. Probably some deeper reason to this, such as activeX forms or something (of which I don't believe this script utilizes), but at any rate it's working now.
My laptop ran the latest windows 7 updates last night and since then all my macros have stopped working. I have had to roll my laptop back to a point before last nights updates and everything is now working fine again. Think there is a major issue with the latest Microsoft update releases.
Sometimes when i hit Enter behind a line to write the next line my cursor jumps down like 300 lines of code within the same Java class which is absolutly annoying.
It jumps just to anywhere within the same file but always somewhere faar below the line i hit enter behind ... so its not jumping to a definition or something like that - it literally just places the cursor to a random point.
Did anyone ever had a similar experience? (I cant find anything on the internet hence i think its either a very easy to fix thing or something for the support).
Like could this be a side effect of defined live templates or something like that?
ANY suggestion could help since i tried out anything i could think of (code completion, live templates, editor settings - nothing looks like it would trigger this behaviour)
Note: I dont like this question at all but i am realy lost right now.
I have not seen any one run into this nor have I seen a bug report on such (and something like that would be a critical). I recommend the following steps:
Upgrade to the latest v14.0.3 if you are not at that version
Invalidate your caches and restart, then wait for IntelliJ to re-index your project (this is a bit of a long shot, but worth the couple of minutes it takes)
File/Application > Invalidate Cache
Disable all third party (i.e. non-bundled) plug-ins and restart
My strongest suspicion is that a 3rd party plug-in is causing the issue.
If this solves the issue, isolate the plug-in causing the issue and contact the developer.
If none of the above work, provide as much detail as you can about the issue as #Makoto suggests. What type of file; what are you doing; OS; IDEA version; etc, etc.
Since I started using CocoaPods, I've been having weird location related messages all the time, and some arch-related ones too.
I've been trying the whole day to figure out why it was happening, until I create a new Xcode project from scratch and realize the issue wasn't project-related all along.
Here's what's happening:
I always get those everywhere as well:
Not sure if related but I get those often too:
Anybody has those as well? What should I do?
Thanks!
I had to switch Build Active Architectures Only for debug to Yes and it let the build run.
I know this is a site more for coding questions, but I have been having a problem with my game crashing for about two weeks now, and Apple hasn't even begun to be helpful in solving the issue or even identifying what it could be. I was hoping maybe someone has experienced something similar and could at least get me pointed in the right direction.
For about a week I had a problem with Xcode crashing every time i accessed a current file (gameboard.m) in my game. This file had existed in my game for months and NEVER caused a crash and never did until a few days after I installed Xcode 5. Whenever I would be working, and click on my gameboard.m, it would, with increasing frequency, crash xcode. When looking at activity monitor, my free ram would go from 5gigs to about 10 mbs, and I would have to force-quit xcode.
After gameboard.m would crash xcode, it would crash xcode upon opening every time after that. I found a temporary fix for the issue by duplicating my file, going into it and deleting the gameboard.m file, then copy and pasting it from the previous version and re-importing it.
Sometimes I could click on gameboard.m and it would open just fine, but then if i press Cmd+Opt+Shift+Left to collapse all my methods, THAT would crash xcode. Every time xcode crashes its the same thing, Ram goes to 0, freezes until force-quitted. After the first week and about 30 copy-pastes fo my game, my quick fix stopped working and I couldnt open ANY file on my desktop, including files I havent opened in months.
So far I've submitted a bug ticket, to which i have gotten no replys besides asking for additional crash reports, I've reinstalled xcode MANY times, created a new user and tried working on that, and am about to reinstall my OS. I'm trying to figure out if it is a code related problem, or a hardware problem that needs to get fixed. I know I have some memory leaks in my game which I am trying to address right now (I've been teaching myself how to program since the start and this has been a gaping hole in my education until now. Any good source material you guys know of point it my way!!)
Side question: If you have a memory leak, when does the computer take back over the allocated ram? Exiting simulator? Restarting computer?
Again, i know this is a bit of an unusual question for SO, but I've been unable to do any work for 2 weeks now and I cant see any end in sight, so any help or ideas i can get from you guys would be very helpful. Thank you!!
The most common way to resolve Xcode crashes is to clear out the derived data directory. Go to Preferences>Locations to find out where it is. Delete the whole directory tree. The default is ~/Library/Developer/Xcode/DerivedData but it may be different for you.
That said, the fact that this continued even when you were working as a different user is troubling, since by default the derived data directory is per-user, but it is possible you've set it to a single place.
I'm assuming by 'bug ticket' you mean the RADAR system (with its new facelift). If this is really preventing you from working on your app and that is critical, what you need to do is file a Technical Support Incident. You get 2 with your developer account, and you can buy 2 more at any time. This will put you in touch with an apple engineer that will focus on finding a solution to your problem as quickly as possible. I've only had to use it twice, and both times they had a solution for me within 48 hours.
I solved this by closing the project, then opening only the offending file in Xcode 5. Then 'Save' and the project then opened fine!
My Xcode was crashing every time I opened it for the last opened project. I got the issue resolved by following the following steps took from here.
Open a Finder window and navigate to your project
Right-click on the .xcodeproj file (it’s a package actually)
Select Show Package Contents
A new window appears
Delete a folder called xcuserdata
Also, delete scuserdata folder from project.xcworkspace inside the .xcodeproj file
I was converting VB6 to VB.NET and now I came across this warning.
I made research before and the result is comment relate statement then add new code if necessary. it is so far so good until I faced an others problem that after comment.
I commented obsolete warning but it made AxMSFlexGrid Array.AxMSFlexGrid Array.GetIndex not found(I got 7 warning about this). The problem made the design view can not show fully which just like the following picture. http://chanmingman.files.wordpress.com/2011/06/couldfindtype.jpg
But no longer, I don't know what happen or what have I done, it gone.
I want to know why. Anyone came across this situation like that?
It is obsolete in .Net 4. That means it works now, but it might be removed in future versions of .Net. You should probably just leave it, since you are having trouble understanding the code.