Error in WPF application

We are using the windows forms webbrowser control in a WPF client
application.

Very rarely we get the following error message:

Message Attempted to read or write protected memory. This is often an
indication that other memory is corrupt.

Stack Trace:
at MS.Win32.UnsafeNativeMethods.DispatchMessage(MSG& msg) at
System.Windows.Threading.Dispatcher.PushFrameImpl(DispatcherFrame
frame) at System.Windows.Threading.Dispatcher.PushFrame(DispatcherFrame
frame) at System.Windows.Threading.Dispatcher.Run() at
System.Windows.Application.RunInternal(Window window) at
System.Windows.Application.Run(Window window) at
System.Windows.Application.Run()

Did anyone encounter this kind of problem with a WPF application using
the WebBrowser control?

If so, how did you solve that problem?

(Using the WPF WebBrowser control is not an option since we need
specific functionality from the winform version)

Thanks,
Hans.

--

Nicholas
Thu Aug 28 10:48:09 CDT 2008

Hans,

Is this on a clean test machine, or is it on a client machine, where the
user might have things such as browser helper objects installed? If it is
the latter, then I would think that those might be the cause, and you should
look there.


--
- Nicholas Paldino [.NET/C# MVP]
- mvp@spam.guard.caspershouse.com

"Hans van Kruijssen herbalife.com>" <hansvk<ADD> wrote in message
news:uPzs2aICJHA.2480@TK2MSFTNGP02.phx.gbl...
> We are using the windows forms webbrowser control in a WPF client
> application.
>
> Very rarely we get the following error message:
>
> Message Attempted to read or write protected memory. This is often an
> indication that other memory is corrupt.
>
> Stack Trace:
> at MS.Win32.UnsafeNativeMethods.DispatchMessage(MSG& msg) at
> System.Windows.Threading.Dispatcher.PushFrameImpl(DispatcherFrame
> frame) at System.Windows.Threading.Dispatcher.PushFrame(DispatcherFrame
> frame) at System.Windows.Threading.Dispatcher.Run() at
> System.Windows.Application.RunInternal(Window window) at
> System.Windows.Application.Run(Window window) at
> System.Windows.Application.Run()
>
> Did anyone encounter this kind of problem with a WPF application using
> the WebBrowser control?
>
> If so, how did you solve that problem?
>
> (Using the WPF WebBrowser control is not an option since we need
> specific functionality from the winform version)
>
> Thanks,
> Hans.
>
> --
>

Hans
Thu Aug 28 13:17:48 CDT 2008

Nicholas Paldino [.NET/C# MVP] wrote:

> Hans,
>
> Is this on a clean test machine, or is it on a client machine, where
> the user might have things such as browser helper objects installed?
> If it is the latter, then I would think that those might be the
> cause, and you should look there.

Thanks for the answer. This is happening on a terminal server with no
browser helper objects. The only thing that I can think of is a number
of (internally developed) old activex controls that are used within the
web pages.

Do you think that an activeX control behaving badly inside a browser
control could cause the protected memory access error?

Thanks,
Hans.
--