mist.exe crashes on Windows 10 Technical Preview

[erezwanderman]

(Copied from here ethereum/go-build#5)
I managed to get it built.
When I run ethereum.exe it starts fine:

C:\Ethereum\go\src\github.com\ethereum\go-ethereum\ethereum>ethereum
Qt: Untested Windows version 6.4 detected!
2014/10/07 02:10:17 [CLI] identity created
2014/10/07 02:10:17 [CHAIN] Last block (#0) 08436a4d33c77e6acf013e586a3333ad152f25d31df8b68749d85046810e1f4b
2014/10/07 02:10:17 [CLI] Starting Ethereum(G)/v0.6.7/windows/go1.3.3
2014/10/07 02:10:17 [REACTOR] started
2014/10/07 02:10:17 [SERV] Ready and accepting connections
2014/10/07 02:10:19 [SERV] Server started

But when I run mist.exe it pops a message "mist.exe has stopped working. Windows is checking for a solution to the problem".

The machine is running in VirtualBox and I'm connecting to it through Remote Desktop. Could be a graphics/driver/qt problem. I'll try to run it when connected to the terminal tomorrow.

[erezwanderman]

Crashes the same way when connected directly to the VM.

[erezwanderman]

Found it crashes on main.go line 74: qml.Run(run)
Might be related to go-qml/qml#109

[obscuren]

Thanks. We're looking in to windows issues. Unfortunately Windows has quite a few problems :-(

[geraldstanje]

@obscuren can you help to debug this?

[erezwanderman]

After adding C:\Qt\Qt5.3.2\5.3\mingw482_32\bin to the PATH (something I should have done in the first place) it still crashes, but takes more time. Now output is:

2014/10/12 01:08:44 [CLI] identity created
2014/10/12 01:08:54 [CHAIN] Last block (#0) 08436a4d33c77e6acf013e586a3333ad152f25d31df8b68749d85046810e1f4b
2014/10/12 01:08:54 [CLI] Starting Mist/v0.6.7/windows/go1.3.3
2014/10/12 01:08:54 [REACTOR] started
2014/10/12 01:08:54 [SERV] Ready and accepting connections
2014/10/12 01:08:54 [SERV] Server started
2014/10/12 01:08:54 [JSRE] started
2014/10/12 01:08:55 [SERV] Added peer (207.12.89.101:30303) 1 / 10 ([])
2014/10/12 01:08:56 plugin.cpp:52:
WARNING: This project is using the experimental QML API extensions for QtWebKit and is therefore tied to a specific QtWebKit release.
WARNING: The experimental API will change from version to version, or even be removed. You have been warned!

ASSERTION FAILED: uncommittedMemory.State == MEM_RESERVE
wtf\StackBounds.cpp(194) : void WTF::StackBounds::initialize()
1   5d002ddf
2   5ce1d7ed
2014/10/12 01:08:57 [SERV] Added peer (65.34.194.20:30303) 2 / 10 ([eth])

[obscuren]

That's indeed the issue. Somehow WTF (Web Template Framework) is bonkers on Windows.

[erezwanderman]

So WTF is the real WTF?

[obscuren]

Good question :-)

[erezwanderman]

Further investigation: On Windows 7, 32 bit:
Qt 5.2.1 works well!
Qt 5.1 is too old for Mist
Qt 5.3.2 (and probably 5.4.0) fail because of WTF bug.

On Windows 10 Technical Preview x64:
It dosen't work with any Qt version. Probably a bug in the OS or Qt.

So maybe this need to be split into two issues.

[fjl]

That looks like a good resolution. Let's simply document Qt 5.2.1 as the only compatible version and ship that QT version with mist for 1.0.

[erezwanderman]

Yes, but also make sure go-qml or Qt know about the issues so they will solve them, and newer versions will work in the future.

[erezwanderman]

Opened issue: QtWebKit WebView crashes on Qt 5.3.2
go-qml/qml#116

[obscuren]

Mist is now using Qt5.4 which removes the dependency on WebKit (and adds Chromium).

Any volunteers for Qt5.4 on windows? :)