Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

53 Crash running x64 build on processors that do not support vmovaps #1819

Closed
JohnGalt1717 opened this issue Sep 28, 2016 · 7 comments

Comments

@JohnGalt1717
Copy link

commented Sep 28, 2016

Just what it says. Absolutely nothing in the log file when it crashes.

I need to use this build because of the major problems with flickering etc. with gpu.

I've tried multiple different locations in the form to set address from loaded, constructor after initilizecomponent and browser_IsBrowserInitializedChanged event and in every case it just crashes to the desktop.

I have a sample app that works with 51 and crashes when upgrading to 53 pre nuget if needed.

@amaitland amaitland changed the title 53 Pre0 - Browser.Address = <string Url> on Wpf causes crash to desktop. 53.0.0-pre01 - Browser.Address = <string Url> on Wpf causes crash to desktop. Sep 29, 2016

@amaitland

This comment has been minimized.

Copy link
Member

commented Sep 29, 2016

@amaitland amaitland added the upstream label Oct 9, 2016

@amaitland

This comment has been minimized.

Copy link
Member

commented Oct 11, 2016

CEF issue is https://bitbucket.org/chromiumembedded/cef/issues/1999/windows-2785-crash-running-x64-build-on also see https://bugs.chromium.org/p/chromium/issues/detail?id=654213 for information on the upstream issue. This problem doesn't affect the x86 version.

@amaitland amaitland changed the title 53.0.0-pre01 - Browser.Address = <string Url> on Wpf causes crash to desktop. 53+ Crash running x64 build on processors that do not support vmovaps Oct 14, 2016

@amaitland

This comment has been minimized.

Copy link
Member

commented Oct 14, 2016

Problem affects WinForms, WPF and OffScreen.

@amaitland amaitland added this to the 55.0.0 milestone Oct 19, 2016

@amaitland

This comment has been minimized.

Copy link
Member

commented Oct 19, 2016

master has been updated, this appears to be resolved in the 2840 branch. Tagging this as 55.0.0 as it will be resolved in that release. For now build your own version from master, use an x86 version or roll back to 51.

@amaitland amaitland closed this Oct 19, 2016

@JohnGalt1717

This comment has been minimized.

Copy link
Author

commented Oct 20, 2016

That's excellent news!

@amaitland amaitland changed the title 53+ Crash running x64 build on processors that do not support vmovaps 53 Crash running x64 build on processors that do not support vmovaps Oct 21, 2016

@keepWalking

This comment has been minimized.

Copy link

commented Oct 17, 2018

master has been updated, this appears to be resolved in the 2840 branch. Tagging this as 55.0.0 as it will be resolved in that release. For now build your own version from master, use an x86 version or roll back to 51.

This bug is still there with latest version: 67.0 for x64 build, no plan to fix?

@amaitland

This comment has been minimized.

Copy link
Member

commented Oct 17, 2018

This bug is still there with latest version: 67.0 for x64 build, no plan to fix?

This bug was fixed in CEF long ago. If your experiencing an issue it's very unlikely to be this. You should test with cefclient. You should read https://github.com/cefsharp/CefSharp/blob/master/CONTRIBUTING.md#cefsharp-vs-chromium-embedded-frameworkcef in detail.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants
You can’t perform that action at this time.