-
Notifications
You must be signed in to change notification settings - Fork 20.3k
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
mist.exe crashes on Windows 10 Technical Preview #135
Comments
Crashes the same way when connected directly to the VM. |
Found it crashes on main.go line 74: |
Thanks. We're looking in to windows issues. Unfortunately Windows has quite a few problems :-( |
@obscuren can you help to debug this? |
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:
|
That's indeed the issue. Somehow WTF (Web Template Framework) is bonkers on Windows. |
So WTF is the real WTF? |
Good question :-) |
Further investigation: On Windows 7, 32 bit: On Windows 10 Technical Preview x64: So maybe this need to be split into two issues. |
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. |
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. |
Opened issue: QtWebKit WebView crashes on Qt 5.3.2 |
Mist is now using Qt5.4 which removes the dependency on WebKit (and adds Chromium). Any volunteers for Qt5.4 on windows? :) |
…cket p2p/sim: configurable unix socket read/write buffer size
* syncservice: log error on unknown topic * typo: fix
* cmd, consensus, eth, ethstats: add protocol interface into consensus to support custom messages * params: add Istanbul consensus engine config to ChainConfig * cmd/*: add Istanbul command line flags * consensus/istanbul, eth: add Istanbul configuration * node: add an interface to retrieve node key from config * core/types: add Istanbul specific block hash calculation * internal/web3ext: add Istanbul JS RPC API * consensus: add Istanbul consensus engine interface * consensus/istanbul: Istanbul core implementation * consensus/istanbul: add tests for Istanbul core * consensus/istanbul: common Istanbul interfaces and types * consensus/istanbul: Istanbul validator set implementation * consensus/istanbul: Istanbul consensus backend implementation * core, les, eth, miner: Istanbul consensus integration * cmd/*, core, params: add ottoman testnet * Address comments * Fix Istanbul lint (ethereum#137) * Remove unused vars for lint * Remove unnecessary conversion * Don't propose empty blocks with Istanbul (ethereum#134) * Make istanbul.Backend a public type * Don't mine empty block with Istanbul engine unless necessary * PR comments * Revert to original order * Add test fixes * PR comments * Update the expected hash given that celo headers have a different payload with BlockSignature * Make Istanbul's Seal asynchronous Originally, when Istanbul was written, the Seal method was synchronous, i.e. it would return when the sealing process was done (or cancelled). Now that is no longer the case, in fact the miner expects the Seal to return to be able to respond/intiate other Seal's. This commit allows Istanbul to do so. * Notify the Istanbul engine of new ChainHeads During the merge, we removed this crucial line, where the worker will notify the Istanbul engine of new chain heads that crucially allow its peers to increse the sequence number for the next Seal. * Apply celolatest syncmode mods to Istanbul * [Istanbul] Seal/NewHeadChain fixes (ethereum#147) * Make Istanbul's Seal asynchronous Originally, when Istanbul was written, the Seal method was synchronous, i.e. it would return when the sealing process was done (or cancelled). Now that is no longer the case, in fact the miner expects the Seal to return to be able to respond/intiate other Seal's. This commit allows Istanbul to do so. * Notify the Istanbul engine of new ChainHeads During the merge, we removed this crucial line, where the worker will notify the Istanbul engine of new chain heads that crucially allow its peers to increse the sequence number for the next Seal. * Fix test * Fix test
…ients Fix `state.New` for old blocks
Overall strategy is: * we assume operations on well-formed ciphertexts don't fail * for operations we assume shouldn't fail, we use asserts * for operations that we assume can fail, we use return codes Essentially, allowing malformed ciphertexts from txns means these ops could fail at some point in the lifetime of a cihpertext and/or on ciphertexts that are produced from the original one: * deserialization or ciphertexts * decrypt * any FHE operation * serialization We assume the following ops don't fail if all inputs are well-formed: * deser of FHE keys * encryption We also assume that tfhe-rs failures are always deterministic. That allows us to not stop the node on such a failure and assume that all nodes have the same behaviour, leaving nodes in sync. Also, do not use Go finalizers anymore. Instead, ser/deser ciphertexts across the C/Go boundary. That avoids complications with finalizers and memory management. However, it has a performance overhead and we need to be extra careful that we free all C memory manually.
cmd: Fix typos
fix parse enr ip
Merge branch 'forking-incident-fix' @hash-laboratories-au
(Copied from here ethereum/go-build#5)
I managed to get it built.
When I run ethereum.exe it starts fine:
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.
The text was updated successfully, but these errors were encountered: