RE: AccessViolationException was unhandled

Alex (s-code) — Tue, 10 Feb 2009 19:14:23 GMT

I cannot reproduce this problem using the latest ViewerX build. Could you please send us a sample code that we could use to reproduce the crash?
Please email it to support@s-code.com

RE: AccessViolationException was unhandled

teamwork — Tue, 10 Feb 2009 13:29:17 GMT

I have the same error - I understand what you're saying, but am not clear on how to implement it.

Can someone give me an example of how this can be fixed?

RE: AccessViolationException was unhandled

Airegin — Thu, 22 Feb 2007 11:25:15 GMT

Works great! No Repro. Thanks.

RE: AccessViolationException was unhandled

Support (s-code) — Thu, 22 Feb 2007 00:09:39 GMT

Hi,
could you give a try to a fixed version attached and check the bug is still reproducible.

AccessViolationException was unhandled

Airegin — Wed, 21 Feb 2007 15:45:06 GMT

Here's the repro steps:

Users inits connection to a server that is off (ConnectAsyncEx)
Before timing out, user inits connection to another server.
Control connects to valid server
.5-1 second after successful connection, exception occurs.

System.AccessViolationException was unhandled
Message="Attempted to read or write protected memory. This is often an indication that other memory is corrupt."
Source="System.Windows.Forms"
StackTrace:
at System.Windows.Forms.UnsafeNativeMethods.CallWindowProc(IntPtr wndProc, IntPtr hWnd, Int32 msg, IntPtr wParam, IntPtr lParam)
at System.Windows.Forms.Nativewindow.DefWndProc(Message& m)
at System.Windows.Forms.Control.DefWndProc(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.AxHost.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativewindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativewindow.WndProc(Message& m)
at System.Windows.Forms.Nativewindow.DebuggableCallback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg)
at System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(Int32 dwComponentID, Int32 reason, Int32 pvLoopData)
at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)
at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)
at System.Windows.Forms.Application.Run(ApplicationContext context)
at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.OnRun()
at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.DoApplicationModel()
at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.Run(String[] commandLine)
at VNC_Command_Console_2.My.MyApplication.Main(String[] Args) in 17d14f5c-a337-4978-8281-53493378c1071.vb:line 81
at System.AppDomain.nExecuteAssembly(Assembly assembly, String[] args)
at System.AppDomain.ExecuteAssembly(String assemblyFile, Evidence assemblySecurity, String[] args)
at Microsoft.VisualStudio.HostingProcess.HostProc.RunUsersAssembly()
at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart()

The VNC Manager - SmartCode Solutions Forum / SmartCode ViewerX VNC Viewer ActiveX / Bug Reports / AccessViolationException was unhandled / Latest Posts

RE: AccessViolationException was unhandled

RE: AccessViolationException was unhandled

RE: AccessViolationException was unhandled

RE: AccessViolationException was unhandled

AccessViolationException was unhandled