I just upgraded a legacy app from wxWidgets 2.8.x to 2.9.3
The log timestamps are now 5 hours in the past!
This screenshot was taken at 1:40PM in EST, as shown in the taskbar clock display.
I wouldn't mind so much if the timestamp was UTC, but it seems to be using a timezone somewhere in the Pacific.
How can I alter this?
http://trac.wxwidgets.org/ticket/14148 seems to be experiencing the same problem. See if you can get any help on that issue.
As suggested by a careful reading of the discussion on that ticket, this is a bug in wxWidgets v2.9.3, fixed in v2.9.4.
Related
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.
I just updated to the latest IntelliJ (135.666) and all of a sudden I'm getting a 2048 popup every half hour or so. I get the attempt to promote relaxing on regular intervals, but this?
So is this an actual IDE thing (and how do I disable this annoyance) or is it extra functionality of a plugin that I've never seen before today.
I've looked through all settings but can't seem to find anything.
As this seems to pick up interest I'm going to answer it myself:
It's for April Fools and it will cease at the end of the day.
According to Jetbrains it's only implemented in the last EAP and you cannot turn it of. Their advice is to use the previous version if it's too annoying.
See their blog entry
As you are working on the IDE, suddenly it has no reaction, the whole IDE become inactive and can not operate on it, but with high CPU usage, If you kill the process from Windows Task Manager, after it launched, all modified lost since your last edit. This problem occurs every now and then.
My environments:
Windows 7, Intel i7, 16GB RAM, IDEA 12.1.6 with auto save enabled.
Did anyone come across this problem before, it's to bad as my changes lost and i have to rewrite it after restarted.
You'll want to upgrade to v12.1.6 as 12.1.5 had a major bug in it that was fixed in 12.1.6. The bug prevented compiling of code in some circumstances. 12.1.6 was released only a few days after 12.1.5. That may not be the cause of your issue, but is still good advice.
Other than that, the 12.1.x line has been very stable. I think your issue is an isolated case as I have not seen any mention of it in the IntelliJ IDEA forums or here. Often times, such deadlocks are caused by third party plug-ins. Take a look in the logs (Help > Show Log) to see if it has any information that explains the hang. Also, if IDEA becomes non responsive, it automatically logs thread dumps in the log directory. Those may have some information.
If you experience the issue again, you may want to disable any third-party plug-ins to see if that resolves it. If it happens frequently, you can take a CPU Snapshot as described in this document and submit it to the JetBrains.
Lastly, I recommend you tweak the following setting: File > Settings > [IDE Settings] > General > Save files automatically if application is idle for x sec." Set it to 15 or 30 seconds. (You don't want to go too low). This will help reduce any loss of work in the event of a hang (which after 10 years of daily IDEA use I can attest to as being very rare.)
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 accidentally clicked discard changes (thought I had a snapshot)... anywho, before I start up of the 7 hours of lost time, does anyone know if there is a 'trash can' or something hiding in Xcode that may have the file I discarded? Or is there any other way to get it back?
Thanks
This is a perfect job for Time Machine.