I just noticed this Apple generated error in console, which made me laugh:
25/03/2015 10:23:04.000 kernel[0]: process Fire[65350] thread 13877807 caught burning CPU! It used more than 50% CPU (Actual recent usage: 99%) over 180 seconds. thread lifetime cpu usage 90.689805 seconds, (90.355620 user, 0.334185 system) ledger info: balance: 90016515382 credit: 90665649778 debit: 649134396 limit: 90000000000 (50%) period: 180000000000 time since last refill (ns): 90171458054
Generated spindump report in case it it useful (there are three other similar ones from yesterday). Fire burns.txt (24.2 KB)
was this during compile? full CPU load would be normal and expected there. Was the UI responsive or did it hang? if it hung, did it recover eventually,or did you have to kill it?
From the dump, it looks like the Mono GC was pretty busy (which should’t affect the main thread)
I’m not sure exactly what it was doing at that point as I didn’t notice any unresponsiveness, I just noticed it in console which I have running on another monitor (also now, activity monitor), but then it is a rather powerful beast.
I did have a moment a few minutes later (after I’d logged this) when the app ran in the simulator and it didn’t get past the launch screen, and CMD-. didn’t kill it, and I couldn’t edit in Fire so I closed Fire and got the attached, if it helps.untitled 2.txt (58.9 KB)
PS, can you add the .crash extension to Talk for files to drop in here to save a couple of steps?
I just had this again, whilst running on the simulator. Again, the launch screen was shown but it didn’t get any further (different app to previous one). I could see in activity monitor, Fire was using 99% of CPU. This time, rather than closing the simulator, I left it and waited. Fire then was reported for being caught burning as above, and Fire crashed (and burned) with attachedfire crash.txt (72.9 KB)
