(0x80004005): Invalid access to memory location

[dariusclay]

This issue happens when compiling LiveScript files. Restarting Visual Studio clears the problem, but then it starts back up after a time.

Here's the stack trace

7/24/2014 1:29:57 PM: LiveScript: Compiling app-main.ls
7/24/2014 1:29:58 PM: An exception was thrown when compiling app-main.ls: System.Net.NetworkInformation.NetworkInformationException (0x80004005): Invalid access to memory location
   at System.Net.NetworkInformation.SystemIPGlobalProperties.GetAllTcpConnections()
   at System.Net.NetworkInformation.SystemIPGlobalProperties.GetActiveTcpConnections()
   at MadsKristensen.EditorExtensions.NodeServer.SelectAvailablePort()
   at MadsKristensen.EditorExtensions.NodeServer..ctor()
   at MadsKristensen.EditorExtensions.NodeServer.<Up>d__0.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at MadsKristensen.EditorExtensions.NodeServer.<CallServiceAsync>d__b.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at MadsKristensen.EditorExtensions.NodeExecutorBase.<CompileAsync>d__0.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at MadsKristensen.EditorExtensions.Compilers.NodeCompilerRunner.<RunCompilerAsync>d__0.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at MadsKristensen.EditorExtensions.Compilers.CompilerRunnerBase.<CompileAsync>d__0.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at MadsKristensen.EditorExtensions.Compilers.EditorCompilerInvoker.<InitiateCompilationAsync>d__4.MoveNext()

WE2013 2.2.7
VS2013 Update 3 RC
Windows 7 x64 Enterprise

[am11]

Thank you for reporting this issue.

Can you please share some sample code which is causing the issue? Would be excellent, if you can create a sample project, which we can work with.

[am11]

@SLaks, looks like it chokes when selecting port.

Any safeguards we can provide in SelectAvailablePort() method to prevent this from happening?

[am11]

@dariusclay can you confirm if you have this hotfix installed: KB 2588507 on your Windows 7 system?

I am not sure if that's relevant (as that one is caused by GetActiveTCPListeners() instead of GetActiveTCPConnections()), but here is what I have found:

http://blogs.msdn.com/b/cie/archive/2013/10/31/compute-emulator-invalid-access-to-memory-location.aspx

This hotfix applies to all versions from Windows Vista to 8. Its fixed in Windows 8.1 onward.

[dariusclay]

@am11 sorry for the late reply. I just looked and that hotfix is not on my system.

here's a very simple script that does cause the issue. Also it doesn't always happen, maybe after compiling a dozen times or so.

'use strict'
require 'angular'
app-main = angular.module 'app-main' [
  require 'ui-router'
  require './modules/admin'
]
  ..config require './common/routes'
  ..run require './common/definition'

module.exports = app-main

[am11]

Actually I am on Windows 8.1 (which doesn't have this issue) and that hotfix applies to Windows Vista, 7 and 8.0 (and the corresponding server editions). Can you install it and see if it fixes this issue?

Thanks.

[dariusclay]

Ok, I applied the patch. I will let you know if the issue crops up again.

Thanks,
Darius

[madskristensen]

@dariusclay Any update on this?

[dariusclay]

After installing the KB update I haven't seen the issue. However, running
the current stable version of WE2013 and VS2013 SP2 at home doesn't present
the issue either (without the KB update). Just food for thought.

[am11]

@dariusclay, that is because the current stable doesn't has the service-based architecture for node.js-based features, which is recently implemented (available via nightly builds).

[dariusclay]

Awesome, well the KB works then. Thanks everyone!