Emulyator / open-webkit-sharp

Automatically exported from code.google.com/p/open-webkit-sharp
GNU Lesser General Public License v3.0
0 stars 0 forks source link

System.AccessViolationException #115

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Sometimes when caling .Reload() on instance of WebKitBrowser
2. Sometimes, when running some JS scripts (specially talking about 
joint.all-min.js)

What is the expected output? What do you see instead?
I'm expecting rendering web page. Instead of this, I got 
System.AccessViolationException, with stack trace:

   w System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg)
   w System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(Int32 dwComponentID, Int32 reason, Int32 pvLoopData)
   w System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)
   w System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)
   w System.Windows.Forms.Application.RunDialog(Form form)
   w System.Windows.Forms.Form.ShowDialog(IWin32Window owner)
   w System.Windows.Forms.Form.ShowDialog()
   w WPB11.Program.Main()

What version of the product are you using? On what operating system?
Windows 7, 64bit. OpenWebKitSharp 2.8 with Binary 2.
BUT - I have tested it on Windows XP and with Example project (.NET 4).
I also have tested it with projects downloaded from net: 'GT Web Browser 2 
Setup' and 'GTLite Navigator setup 1.1.3'. All of them have the same problem 
with System.AccessViolationException

Please provide any additional information below.
This error makes my application useless and in fact I can't use it.
Can You please do something with this error? I read some other threads with 
this problem but I didn't found any solution.
As I mentioned before - with this error, I'm unable to deploy a stable version 
of application.

Related issues: 
Issue #99: http://code.google.com/p/open-webkit-sharp/issues/detail?id=99
Issue #65: http://code.google.com/p/open-webkit-sharp/issues/detail?id=65

Original issue reported on code.google.com by mac.lip...@gmail.com on 5 Jun 2012 at 9:40

GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago
I've received a comment from 'benoit':  Try building with "Allow unsafe code", 
it worked for me.

But unfortunately this didn't helped for me. If Webkit is being used by Safari 
and Chrome... then why this dll crushed with c# and doesn't with the Safari and 
Chrome browser? There have to be some solution.

Original comment by mac.lip...@gmail.com on 10 Jun 2012 at 4:46

GoogleCodeExporter commented 9 years ago
As you can see, I deleted the comment as it stopped working for me too after a 
while eveb with "unsafe code".  However, I downloaded the latest Windows build 
directly from the WebKit website: http://nightly.webkit.org/builds/trunk/win/1

I have not had a crash since, so it looks promising.  You just need to copy the 
binaries to your output directory.

Original comment by benoit.v...@gmail.com on 10 Jun 2012 at 4:51

GoogleCodeExporter commented 9 years ago
Can You please provide some instruction what to do after downloading nightly 
build? I've downloaded file 'WebKit-SVN-r119928.zip', after that I've copied 
all '*.dll' files and folders:
* JavaScriptCore.resources
* WebKit.resources
to folder with my application (replacing the old files from the 
open-webkit-sharp). 
Error still occurs when launcing my javascripts, but I must say, that it occurs 
in some other places than before.
I can't say what with the 'refresh' or 'back' buttons - it also crushed the 
application (like other people was also reporting).

Should I do something else?

Original comment by mac.lip...@gmail.com on 10 Jun 2012 at 5:09

GoogleCodeExporter commented 9 years ago
Button 'next'/'previous' still crushes the app

Original comment by mac.lip...@gmail.com on 10 Jun 2012 at 5:12

GoogleCodeExporter commented 9 years ago
I don't use the next/previous buttons in my app.  Is it still an 
AccessViolationException?  If you don't use refresh/next/previous, do you still 
see crashes when executing javascript?

Original comment by benoit.v...@gmail.com on 10 Jun 2012 at 5:25

GoogleCodeExporter commented 9 years ago
The next/previous buttons sometimes (not always) crushes application. And yes, 
there is still the same Exception. Previously, when I was clicking on item, 
javascript that should show an row between two objects, crushes application. 
With new build that You've recommended, after I click button, the arrow shows 
and after that the Exception is being thrown.
Effect is the same.

System.AccessViolationException with stack trace:
   w System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg)
   w System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(Int32 dwComponentID, Int32 reason, Int32 pvLoopData)
   w System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)
   w System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)
   w System.Windows.Forms.Application.Run(Form mainForm)
   w WPB11.Program.Main() w D:\Workspace Visual Studio\mop\WPB11\Program.cs:wiersz 29

Original comment by mac.lip...@gmail.com on 10 Jun 2012 at 5:50