Since installing Xcode 6.1, at times, while debugging and stepping through code statements (obj-c), my computer crashes with a kernel panic in coreaudiod.
Has anyone seen/resolved this somehow ? tia
running in MBP , 16Gb memory (plenty free), no iTunes or audio process running, but process being stepped runs a background music with OpenAL prior to the initial breakpoint.
Related
I recently switched out my AMD Ryzen 7 3800x for a Ryzen 9 5950x. I also purchase and M.2.
I got these today and installed them on my computer. I have an SSD, a hard Drive and now an M.2
I deleted Fortnite from my hard drive and then installed it on my M.2 the game started up fine it played okay no problems
Then I uninstalled Call of duty modern warfare. I reinstalled it along with its launcher on the new M.2
After installation I went to start the game and check out how it runs with the new stuff.
My problem is that every time I try to start the game it loads for 10 seconds then my computer reboots. I cannot even load into the game because the computer just reboots itself.
I have tried uninstalling and reinstalling again,
I tried running as Administrator,
I attempted to reset the M.2 and see is that was the issue,
I also uninstalled and reinstalled fortnite and it worked perfectly fine.
Does anyone have any tips on what to check or what to do? Everything is up to date. I also reset my bios just in case my old overclock settings for the old CPU had something to do with the crashing of this new one, but nothing happened it kept crashing.
I also attempted to install call of duty vanguard and call of duty cold war. Same thing happened with those as well. I then installed a free to play game and it also happened with that.
I am not sure where to go from here. If anyone has any tips on how to fix this I would be more than pleased. Thank you so much
I've recently finished a game that I successfully packaged to Windows 64-bit but then when I ran the .exe file on another computer (the game works on my computer), the file crashes and says: The Game has crashed and will close. There was no error messages or logs, just that.
I searched this up on YouTube, Stackoverflow, and the UE4 Forum but nothing helped. Please help, thanks.
I am currently running a VB application through mono on Raspbian. After a bit of troubleshooting the program boots and appears to be running quite well. However if left to itself for a few minutes the VB application just shuts off. This program runs excellently on the windows pc for any duration. Barring this being an issue with the VB code itself is there any major PI related issues that I may have missed in setting up mono? I set up mono the usual way and am launching via "sudo mono app.exe" in terminal.
Thank you for any insight you may provide into this!
UPDATE: mono just FINALLY threw out an errot to me System.OutOfMemoryException : Not enough memory to complete operation [GDI+ status: out of memory]
UPDATE2: Memory leak, its a code related issue.
Hi to anyone else that runs into this issue. For us it was a memory leak.
Since re-installing Windows 7 Ultimate 64-bit SP1, sometimes processes take a long time to close. This happens most frequently when launching them from VS2010, but it's not limited to that. A common case is a Windows app with a console (/SUBSYSTEM:console) that appears to close correctly, but the console remains open for seconds or minutes. Eventually the "press any key to close" message appears on the console, and the process can be terminated.
How can I diagnose this problem?
I installed Windows 7 Ultimate 64-bit SP1, but this time the vanilla (not N) version
The only driver I manually installed is the NVIDIA display driver, but I've tried multiple WHQL versions
The symptoms closely match the question at
Visual studio debug console sometimes stays open and is impossible to close Even non-console apps are affected, however.
Both native and managed applications suffer from this.
WRONG: I believed only 32-bit processes were affected, but 64-bit ones also suffer.
if a debugger is already attached, and I break while the process is waiting, the debugger
says:
The process appears to be deadlocked (or is not running any
user-mode code). All threads have been stopped.
I can't attach a debugger to a process while its in this state
I can't kill these zombie processes from Task Manager or
ProcessExplorer, even when closing all handles that refer to said
processes. (I can't close lsass.exe's handles, though)
ProcessExplorer says that the hanging function of the only thread
that the each hung process has is ntdll!RtlDosSearchPath_Ustr.
Most of the time I have to close Visual Studio completely to allow
the zombie processes to close.
The last event that Process Monitor sees at the hang in each case is
a Thread Exit, which succeeds, and it looks like the exit takes the
normal amount of time. When the process finally closes, no events
show up.
LiveKd doesn't show anything when I follow the steps outlined at
http://blogs.technet.com/b/markrussinovich/archive/2005/08/17/unkillable-processes.aspx
It seems like a bad driver is the culprit, so I'm going to reinstall Windows soon.
I m having trouble with AIR debug launcher(adl) under win 7 64 bits home familial with AIR SDK runtime 2.7. It sometimes crash and i have no posibilities to understand if its because of my software or not.
Does anybody know how I can get some logs to know why it crashed ?
When its crash, the debugger is going away and i dont know where my software bugged if it did...
I have been testing my software under different SDK under win7 and i still had some adl crash. The software is working correctly under winXP. I suppose it has something to do with win7 and AIR but how can I find any informations on what is going on...?
thanks for any tips...
i have been able to find windows crash dump files. Then i have download windbg. And started debugging air debugger launcher... but im stuck... not good debugging without symbol files... I guess cant do more then that. The error come from an attempt to convert an integer to a unicode string but i dont know why this function is called, by who and when...
sometimes it doesnt crash also.
Finally found some windows crash dump log files. Also started to debug with windbg the AIR. :))) lol