|
|
|
Forum Newbie
      
Group: Forum Members
Last Login: 8/20/2007 2:37:25 PM
Posts: 6,
Visits: 12
|
|
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()
|
|
|
|
|
Supreme Being
      
Group: Administrators
Last Login: 2/5/2010 6:36:52 PM
Posts: 1,146,
Visits: 1,878
|
|
Hi, could you give a try to a fixed version attached and check the bug is still reproducible.
 Kindest Regards, SmartCode Solutions Support
|
|
|
|
|
Forum Newbie
      
Group: Forum Members
Last Login: 8/20/2007 2:37:25 PM
Posts: 6,
Visits: 12
|
|
| Works great! No Repro. Thanks.
|
|
|
|
|
Forum Newbie
      
Group: Forum Members
Last Login: 2/10/2009 1:27:13 PM
Posts: 1,
Visits: 1
|
|
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?
|
|
|
|
|
Forum Guru
      
Group: Forum Members
Last Login: 2/12/2009 8:16:06 AM
Posts: 53,
Visits: 54
|
|
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
Regards, ---- Alex Morozov Chief Software Engineer SmartCode Solutions
|
|
|
|