2

This has happened to me twice now. Windows 8.1 decides to suspend all my processes all of a sudden. Now I know that it does that to Metro apps that are in background. But my regular desktop apps (including Explorer) might be exempted from that, I guess (especially when I'm currently using them).

I could get it to run again more or less by starting Task Manager via Ctrl+Alt+Del, then killing Explorer and starting Process Explorer from there which enabled me to resume all processes again. But I still wonder how this happens in the first place. Specifically I'd like to ask whether that's in any way expected behaviour and what I could do to prevent it from occurring in the future.

My system is virus-free, just in case anyone asks. Yesterday I just tried to run msbuild; after hitting above issue happened. A while ago I don't remember what I tried to do when it manifested, but I didn't think far enough to solve the problem with procexp and ended up restarting the machine.

EDIT: Okay, it seems like starting msbuild triggers this behaviour. No idea why, though.

EDIT2: Apparently only when running it from Far Manager (actually, it's a batch file for me, which calls the vsvars32 batch and runs msbuild afterwards. It runs fine from cmd or PowerShell.

EDIT3: Updating Far Manager to its latest version changed nothing. However, running msbuild directly (not through the batch file) worked even from Far.

For completeness:

  • Far Manager
  • My PATH includes the directory D:\Users\Joey\Batches which contains a batch file msbuild.cmd with the following contents:

    @echo off
    call "C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\Tools\vsvars32.bat"
    msbuild %*
    
  • Then, running msbuild from within Far seems to produce this problem. At least for me, reliably.

9
  • Does this problem happen every time you run msbuild?
    – Ramhound
    Nov 6, 2013 at 13:14
  • No. I merely mentioned it just in case anyone asks what I was doing. I doubt the application is relevant here.
    – Joey
    Nov 6, 2013 at 13:34
  • You need to tell us what triggers this behavior.
    – Ramhound
    Nov 6, 2013 at 13:40
  • If I knew, I'd be a few steps further already. From what I can tell nothing specific I did.
    – Joey
    Nov 6, 2013 at 14:00
  • @Ramhound: It indeed seems to be msbuild. I could reproduce the problem twice in the last half hour. Not once did msbuild run normally.
    – Joey
    Nov 20, 2013 at 20:14

1 Answer 1

1

It was a problem with clink. It has been fixed by now, but only in source, not in a release.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .