ShockwaveFlashObjects gives 'System.AccessViolationException'
-
Hi. I have created an WindowsFormsApplication with multiple forms, and in a form I added an ShockwaveFlashObject and i set it a .swf file. The problem is that when I access two or three forms and come back to this form, it shows me this error message:
An unhandled exception of type 'System.AccessViolationException' occurred in Unknown Module.
Additional information: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.I don't really know how to fix this, I just managed to find out that this is the problem. The ShockwaveFlashObjects was added to toolbox from COM Components.
-
Hi. I have created an WindowsFormsApplication with multiple forms, and in a form I added an ShockwaveFlashObject and i set it a .swf file. The problem is that when I access two or three forms and come back to this form, it shows me this error message:
An unhandled exception of type 'System.AccessViolationException' occurred in Unknown Module.
Additional information: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.I don't really know how to fix this, I just managed to find out that this is the problem. The ShockwaveFlashObjects was added to toolbox from COM Components.
DPaul1994 wrote:
I don't really know how to fix this
Unfortunately it is not easy. You will have to do some, or even a lot of, debugging in order to discover where in the application the access violation occurs. The most likely cause is passing a bad reference to some library method, but you would need a detailed stack trace to start investigating.
-
DPaul1994 wrote:
I don't really know how to fix this
Unfortunately it is not easy. You will have to do some, or even a lot of, debugging in order to discover where in the application the access violation occurs. The most likely cause is passing a bad reference to some library method, but you would need a detailed stack trace to start investigating.
I don't really know how to make such a deep debugging, because it doesn't show me the line where the error occurs, it just shows me that message when I close the application and that's it..If I remove ShockwaveFlashObjects and AxShockwaveFlashObjects from reference and the item from form, it works perfectly, so that is the issue
-
I don't really know how to make such a deep debugging, because it doesn't show me the line where the error occurs, it just shows me that message when I close the application and that's it..If I remove ShockwaveFlashObjects and AxShockwaveFlashObjects from reference and the item from form, it works perfectly, so that is the issue
Like I said: it's not easy. There is no way that anyone can guess the answer for you. You will have to add some code to your application to get more information about what is going on, until you can narrow it down to the general area where the problem occurs. That is when you can start tracing through with your debugger.
-
Like I said: it's not easy. There is no way that anyone can guess the answer for you. You will have to add some code to your application to get more information about what is going on, until you can narrow it down to the general area where the problem occurs. That is when you can start tracing through with your debugger.
-
Like I said: it's not easy. There is no way that anyone can guess the answer for you. You will have to add some code to your application to get more information about what is going on, until you can narrow it down to the general area where the problem occurs. That is when you can start tracing through with your debugger.