!runaway error: could not get process information, 6 - iis

I've got an IIS process CPU issue, for some reason the w3wp.exe always takes 100% CPU. I used to try WinDbg to analyse threads in w3wp dump file, which was very convenient.
But somehow WinDbg is not working now. It keeps showing
could not get process information, 6
when I use !runaway.
The version of sos.dll and clr.dll are correct, and !clrstack works fine. Even .ttime works fine that I can get run time for single thread.
Just !runaway is not working, what did I do wrong?

Well... I suppose I could answer my own question...
The WinDbg I've been using is the UWP version which downloaded from WinStore (WinDbg Preview). That worked fine weeks ago but now we need to do some upgrade.
I download the latest version of WinDbg from this url:
https://developer.microsoft.com/en-us/windows/downloads/windows-10-sdk/
Now everything works fine...

Related

Electronjs + Reactjs | Window server 2012 R2 hangs on app launch (white screen), works fine on windows 10 and windows server 2019

Pretty much title.
Cursor constantly changes from standby to loading, but other then that the screen stays white.
I have tested it on windows server 2019 and it worked, same goes for my local computer which is windows 10.
I tried building a x32 bit version and it crashed.
There is barely any information on the internet regarding older versions, and the one thread I saw mentioned what Ive tried already.
Can anybody point me to the right direction? I'm kinda clueless right now and trying to compare things like .NET Framework and such (although I'm pretty sure it's not related at all?)
Thanks!
EDIT:
I'm getting an error in the event viewer that theres a faulting modoule, and it is ntdll.dll
going to continue research for now!
Just incase anyone sees this and have a similar issue:
1.The desktop on our citrix server was programmed to be located on a network share and not on a physical hard drive, so I had to move it to the proper folder.
2.The application worked only when I placed it on the local drive, and only as a 32 bit application.
I spent two days basically trying everything on a 64 bit application, because when I tested the 32bit one it just crashed, but it turns out they were two seperate issues which are finnaly resolved!

MARS MIPS Simulator freezes when trying to open a file on Linux

I am running MARS 4.5 on Linux Mint with OpenJDK 8 and the program starts up fine and I can create a file. However, if I try to save or open another file, the program freezes and I have to kill the process.
The strange thing is that it worked one time, but after restarting the program, it was back to freezing whenever trying to access the filesystem.
I apologize if this is the wrong place for this kind of question, but I'm not sure where else to post it. If this is the wrong place, let me know and I will remove the question. Thanks for any help.
Switching to the official jdk from Oracle seems to have fixed the problem. I followed these instructions to uninstall OpenJDK and install the official one.

Visual Studio 2017 crashes after 10-20 minutes

For over a month now I've been experiencing problems with VS2017 on my home PC. I even tried submitting the feedback to Microsoft. There's more info about the problems I'm experiencing there.
The problem:
The gist of it is that VS is eating RAM like crazy. As soon as I start opening files, adding new files, using IntelliSense, building or (especially) debugging, the RAM usage skyrockets.
After that it's only a matter of time before the VS crashes and restarts without any error message. Though there are numerous error messages throughout these breif ~20min I have with each session.
Additional details I observed:
Doesn't happen with Python projects, as these don't have to be built constantly. It might be eventually happening if you debug a lot, but I didn't have the chance to check that because most of my Python coding is debugged on an external device
Size of the loaded solution doesn't matter;
UWP and WPF seem to crash the most. Console Projects take longer to crash.
Also affects .NET Core;
It doesn't matter which version of .NET Framework I use;
VS2015 worked perfectly, but I don't have it anymore after the format
What I already tried:
I reinstalled VS;
I refreshed Windows;
I reinstalled Windows;
I checked my drives and RAM for issues - none found;
I switched from Community to Enterprise;
I tried disabling extensions;
I applied some shady hotfix I found somewhere;
Finally, I installed Rider which seems to be the best solution as of now. It still lacks many important features, though.
Is there anything else I can do/try/check? Did anyone experience (and fix) a similar issue?
Cheers!
You get a System.OutOfMemoryException, this means your Visual Studio runs out of free virtual address space (4GB on 64 Bit Windows for the 32Bit Visual Studio because Visual Studio is configured to be large address aware and MS refuses to release VS as 64Bit program which would fix this issue).
To analyze the memory usage, you need to run WPRUI.exe (part of Windows Performance Toolkit (which gets installed by VS2017) for some scenarios, if not, install it on your own), select Reference Set (Note: expand the Resource Analysis entry first to see all options).
and click on Start. Capture the memory usage grow for some 100s of MB and click on Save.
Open the generated ETL with the analyzer (WPA.exe) and analyze what the process devenv.exe is doing.
Also zip the ETL + NGENPDB folder (important) as zip and attach it to your bug report so that Microsoft can analyze it.

Visual Studio 2012 Profiler wont produce any output (Win 8)

I searched both the web and stackoverflow and I feel I'm the only one, so probabyl I'm soing something very simple ver wrong.
I run VS11 (2012) on a Win 8 64 machine and everything is nice and neat, the profiler too seems (!) to work as it should just that at the very end he's never able to show any results. I get an almost empty window which say that there are no data to show.
I used the "Sampling"
What i found browsing the web is a MS article saying the "Sampling" (which I used) is not available, which would explain it, but A) the article was about the Win8 preview and B) I also found some people giving nice examples of using the VS11 Profiler on Win 8 (in Sampling), so I know some people got it working. But how ?
I also tried running VS explicitly as Admin but it didnt make a difference. And yes, Instrumentation is working, but thats of no help for our project, we need Sampling.
I am also having this problem (I'm running Visual Studio Ultimate 2012, Windows 8 x64). It seems that if the program runs very quickly (mine runs under a second), there are no results. I decided to make it run for a few seconds and the sampling profile worked. After scouring the internet I have found some unhelpful webpages - but maybe they will report a fix in the future:
A thread on msdn about this issue
http://social.msdn.microsoft.com/Forums/en-US/vstsprofiler/thread/c609d76c-be22-4ffb-858c-73ccab591a78/
A blog saying that you should use Windows 7 to be able to configure anything for sampling (I hoped to be able to turn the sampling frequency down, but that isn't possible).
http://blogs.msdn.com/b/profiler/archive/2012/12/10/the-visual-studio-profiler-on-windows-8.aspx

Starting a 64bit process from a 32bit app?

I have a WPF 4.0 application that I have compiled for x86. When running on 64bit Win7, I need to start up an on-screen keyboard, located in %windows%/System32/osk.exe. Problem is I can't do it- I get an error 'Could not start On-Screen Keyboard'.
I found this thread:
Unable to launch onscreen keyboard (osk.exe) from a 32-bit process on Win7 x64 which sounds exactly like my problem.
I used all the relevant bits from that post, but the error persists. And even worse, I managed to get a 32 bit version of osk.exe and when I try to start THAT I just get a blank error box- no message at all, just a red 'X'.
So I can't compile my app for AnyCPU (3rd party interop libs), and have read that that might not solve the issue anyways. I have also read that one workaround is to disable virtualization using Wow64DisableWow64FsRedirection, but that this is unsafe. Seems like a lot of effort just to run a little app :(
What can I do to launch this little thing from my app?
Wrapping the offending app in a exe compiled with AnyCPU works fine and seems to be the least painful approach.

Resources