In the screenshot you can see that this time when rubymine froze, it took up ove 130% of the CPU, which doesn't really make much sense. In some cases this number was over 200%.
Any ideas why this issue happens and how to fix it?
Related
I'm using Unity 2017.2.
I have strange problem. When i run my game into the editor it drops the FPS to very low like 5 - 7 FPS. However if i make a build and run the game it runs perfectly without any problems with 150 - 200 FPS.
Here is my profiler:
All is runing fine without any errors. Can you give me any suggestion where the problem can be. I hope somebody faced similar problem before and i'll be able to resolve this.
Taken from this unity forum post, it seems this is a known issue with the editor itself. You can either roll back to the last version, or wait for a bugfix to come out... Although the fix for this has been "expected soon" for awhile now. It is possible that 2017.3 fixed this issue, though. I haven't updated Unity since it came out so I cannot confirm.
About a month ago, I loaded the Android emulator "Andy" on my windows 8 laptop and it seemed to work fine (except it kept kicking me out of Clash of Clans after a couple minutes, but the emulator kept running).
Yesterday, something happened. While in Clash of Clans, the background turned all black and just the small images were visible. This has happened before and I would kill Andy using the X in the upper right corner. I would then restart Andy and things worked OK again.
However, yesterday when this happened, I killed Andy in the same way, but when I tried to restart Andy the frame would display for a second or two and then go away.
I figured that a bit got twisted somewhere, so I uninstalled that version of Andy and downloaded and installed a newer version, but I get the same results.
I checked the web and the closest I came was "Andy won't launch on windows 8". The suggested solution was to roll back the display driver. I did that with the same results.
I figure that there may be a flag somewhere that thinks Andy is running, so it shuts down any new version, but that is just a guess.
Has anyone else run into this problem?
If so what was the solution?
Try to change the compatibility setting to windows 7/8
I started noticing that it was taking several minutes (5-10) to build and run apps on my iPhone 4S from Xcode. I was running XCode 4.5.2 and iOS6.0 on my 4S and decided to figure out the problem. There was another similar question posted here but it was closed without a definitive answer. (which is a shame since this is a valid concern for folks.) I am reposting the question to explain what I observed. Hopefully it will help someone.
First I rebooted my Mac after several impatient attempts to install a relatively small app seemed to hang. I tried removing all of my old provisioning profiles from my Mac and my iPhone thinking I was having trouble with expired certs/profiles. I tried a few more times and decided to let it just hang to see what happens. It eventually launched the app on my device after about 5-10 minutes. I Googled around and found some hints that maybe I should try rebooting my iPhone and re-synching with iTunes. (I had already made an unsuccessful attempt at synching which also seemed to take forever.) On my next attempt to synch I decided to remove some larger apps (700+MB) to clear space since I was down to my last GB.
Things were still slow so I decided to reboot my iPhone and then re-synching it. I rebooted my phone and went to sync in iTunes again and this time the sync went quickly. I had cleared an extra 3+GB leaving me about 4+GB of free space. I restarted XCode and my app is now installing quickly.
My take-away is such that I believe there may be extra daemons running over time on the device and restarting my phone is what ultimately helped restore install times. Also, I'm not sure if clearing space helped or not. I would like to know what the root cause/solution is but that depends on others having similar experiences and responding.
I was propted by apple to upgrade my debugger settings yesterday, In doing so I have some how broken xcode.
When ever I now try to load an application (dosn't matter what version of the simulator I am using) Xcode and my simulator both freeze up. then the rainbow loader just sits their constantly turning over.
Is there any way to fix this? I'm really stuck and don't know what to do as it dose not seem like a very common problem from all the research I have done to fix this.
I am running the latest version of xcode 4.3.2 (4E2002) and using 5.1 simulator.. and have tried 4.2 simulator to the same effect.
any help in getting my xcode back up and running would be massively appreciated.
Okay so I figured out what the problem is but not a real solution...
Basically the error started happening when I was prompted by xcode to update my debugger to the LLDB version. this is what cause my simulator to keep crashing xcode.. or vice versa honastly I still dont know why this is happening but yea...
so.. what I did to get this simulator working again was go to Product>edit scheme> debugger then changed from LLDB back to GDB.. this solved my issue for now... however I need to figure out why LLDB is not working and what I should do leading into the future. hope this helps someone else.
I have facing this problem too but I got a solution either you said its temporary ... some time ios 5.1 simulator hangs when I shifted to the ios 4.1 sdk its a common practice for the developer to check it I have simply first close the simulator and again start it and then reset all the content in the preference area that its resolved my issue .. check it might be you also got resolve for apply this trick or technique.
Thanks
In my case, was too many old breakpoints tracks (788), even to deleted files, I just clean it and now it runs perfect, I hope it helps.
A picture to illustrate:
been using the gwt plugin in eclipse for about a year, has worked pretty fine.
However, i recently upgraded to OSX lion, and i also upgraded intellij to latest version.
Now, i have a standard gwt project. I have historically been able to start it with the devconsole, change stuff and reload page in firefox. (using firefox5 currently)
But now, i can only start it, but as soon as i reload page, devconsole crashed. Yesterday it just hung, this morning i upgraded to GWT2.4 and now i just get permgen space outofmemory on first reload. I have the memory settings set to 1024m!
If someone could give me pointers it would me much appreciated...
I experienced that same issue after upgrading to Lion. I believe it has something to do with the memory management of OSX, not Eclipse or GWT. It was a source of huge inconvenience to me, and the benefits of the Lion upgrade weren't enough to justify dealing with an impaired capacity for development, so I rolled back to Snow Leopard. That resolved the problem.
I've since tried (unsuccessfully) going back to Lion and using different browser combinations, including Safari and Chrome, but Firefox still seems to be the best choice if you're using Lion- Chrome is exceptionally slow with GWT (oddly), and Webkit in general seems to not support some of the features GWT offers, so Safari's out.
I say go back to Snow Leopard, unless there's something preventing you from doing so. Good luck, and please keep us updated if you figure out a workaround.
Answering my own question since i've found well, not an answer but a workaround.
In intellij, i changed the agent (only using one in development to speed things up) from gecko1_8 to safari, and used chrome.
As i mentioned, the console crashed in firefox on every reload, in Chrome i'm at 30 page reloads/recompiles and not a single console crash!
It also recompiles faster than in FF.
Have no idea why it works so crappy in FF though...
You can fix it - just add -XX:MaxPermSize=384m for jvm.