New install of Viscosity crashes on startup

Got a problem with Viscosity or need help? Ask here!

RobinsonWM

Posts: 2
Joined: Fri May 06, 2016 5:47 am

Post by RobinsonWM » Fri May 06, 2016 6:04 am
I just installed Viscosity 1.6.3.1444 for the first time and have never used it before.
When I click the icon in the Start Menu, nothing appears to happen (no application window appears.)

I see this in the Application Log each time I try to launch it:
Code: Select all
Application: Viscosity.exe
Framework Version: v4.0.30319
Description: The application requested process termination through System.Environment.FailFast(string message).
Message: 
Stack:
   at System.Environment.FailFast(System.String)
   at <Module>.()
   at <Module>..cctor()
And if I launch it with a debugger attached, I get:
Code: Select all
CLR: Managed code called FailFast without specifying a reason.
Managed Debugging Assistant 'FatalExecutionEngineError' has detected a problem in 'C:\Program Files\Viscosity\Viscosity.exe'.
Additional information: The runtime has encountered a fatal error. The address of the error was at 0x72da18d9, on thread 0x2eb0. The error code is 0x80131623. This error may be a bug in the CLR or in the unsafe or non-verifiable portions of user code. Common sources of this bug include user marshaling errors for COM-interop or PInvoke, which may corrupt the stack.

An unhandled exception of type 'System.ExecutionEngineException' occurred in Viscosity.exe
I'm on Windows 10 version 1511 with McAfee VSE 8.8 and FireAMP 4.4.1.
I have tried uninstalling and re-installing Viscosity and also restarting my machine.
I also have the OpenVPN client installed on my machine, which works normally.
Are there any steps I can take to correct this problem?

Eric

User avatar
Posts: 1146
Joined: Sun Jan 03, 2010 3:27 am

Post by Eric » Fri May 06, 2016 1:54 pm
Hi RobinsonWM,

These errors occur either because .NET is damaged or something is trying to hook into Viscosity when it runs (which will corrupt the heap and cause Viscosity to crash). The error is occurring before Viscosity itself actually starts.

As a first step, try disabling any Firewall, AV or Debugging tools you have. If this doesn't work, try running a repair on .NET.

https://www.microsoft.com/en-us/downloa ... x?id=30135

Regards,
Eric
Eric Thorpe
Viscosity Developer

Web: http://www.sparklabs.com
Support: http://www.sparklabs.com/support
Twitter: http://twitter.com/sparklabs

RobinsonWM

Posts: 2
Joined: Fri May 06, 2016 5:47 am

Post by RobinsonWM » Sat May 07, 2016 1:39 am
Thanks for pointing me in the right direction! The culprit ended up being the New Relic .NET Agent (x64) with "Profile all .NET applications" enabled. I tried uninstalling it and reinstalling it several times, and this problem consistently happened only when New Relic .NET Agent was installed. In my case I don't need that to be running on my machine, so I'm good for now.

Thanks!
3 posts Page 1 of 1