Open GoogleCodeExporter opened 9 years ago
[deleted comment]
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
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
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
Button 'next'/'previous' still crushes the app
Original comment by mac.lip...@gmail.com
on 10 Jun 2012 at 5:12
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
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
Original issue reported on code.google.com by
mac.lip...@gmail.com
on 5 Jun 2012 at 9:40