Skip to content
Viscosity crashes after installing .net profiler tool.
Got a problem with Viscosity or need help? Ask here!
We have a client who uses the Viscosity VPN client and was trialing the Prefix .NET profiler. They gave us this error message.
Prefix is free if you would like to try reproducing their error.
Thanks
Dan Gidman
Stackify
Code: Select all
Our own software is not crashing so we are trying to figure out if there is any points of interaction or overlap that could cause your program to crash. Part of our deployment of Prefix is the installation of an IIS Profiling module to monitor individual web requests to their box. This is the most likely cause of your app failing if we are the cause. Could you provide any validation or feedback on next steps we could take with the customer? Application: ViscosityService.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()
Faulting application name: ViscosityService.exe, version: 1.6.3.1444, time stamp: 0x57207337
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0x80131623
Fault offset: 0x00007ffc7ea10ac9
Faulting process id: 0x22f0
Faulting application start time: 0x01d1a18b8aa5388b
Faulting application path: C:\Program Files\Viscosity\ViscosityService.exe
Faulting module path: unknown
Report Id: 31fec8df-36d4-485a-9572-bdafb4b3900d
Faulting package full name:
Faulting package-relative application ID:
Prefix is free if you would like to try reproducing their error.
Thanks
Dan Gidman
Stackify
Hi Dan,
Viscosity and ViscosityService have multiple layers of protection to help prevent attacks against the running processes. A side effect of this is profilers will cause a crash like this if they attempt to attach to the process. You will need to add an exemption so your software is not trying to attach to Viscosity in any way to prevent this crash.
Regards,
Eric
Viscosity and ViscosityService have multiple layers of protection to help prevent attacks against the running processes. A side effect of this is profilers will cause a crash like this if they attempt to attach to the process. You will need to add an exemption so your software is not trying to attach to Viscosity in any way to prevent this crash.
Regards,
Eric
Eric Thorpe
Viscosity Developer
Web: http://www.sparklabs.com
Support: http://www.sparklabs.com/support
Twitter: http://twitter.com/sparklabs
Viscosity Developer
Web: http://www.sparklabs.com
Support: http://www.sparklabs.com/support
Twitter: http://twitter.com/sparklabs
Hi Dan,
Possibly, depending if any effects are flowing down into .NET libraries, or socket connections or kernel space is being modified.
Regards,
Eric
Possibly, depending if any effects are flowing down into .NET libraries, or socket connections or kernel space is being modified.
Regards,
Eric
Eric Thorpe
Viscosity Developer
Web: http://www.sparklabs.com
Support: http://www.sparklabs.com/support
Twitter: http://twitter.com/sparklabs
Viscosity Developer
Web: http://www.sparklabs.com
Support: http://www.sparklabs.com/support
Twitter: http://twitter.com/sparklabs
4 posts
Page 1 of 1