-
Notifications
You must be signed in to change notification settings - Fork 35.6k
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
Bitcoin Core 0.12.0 randomly crashes at launch on WinXP SP3 #7674
Comments
What does the crash look like? Is the splash screen just disappearing into nowhere or does an error message pop up? |
Duplicate of #7639 (which was also on XP SP3) |
Always appears the standart windows message: "application will be closed, blah blah blah".
Sometimes it happens during splash screen, sometimes right after the main window opens. |
Could you start Bitcoin-Qt.exe (or bitcoind.exe) with Run Then wait until it crashes and pastebin the output somewhere. And maybe you could also post your debug.log on pastebin.com. |
To rule out some new/changed functionality:
|
still segfaults with -disablewallet also segfaults with -disablewallet -listenonion=0 -connect=192.168.42.69 |
What about |
-connect=0.0.0.0 also segfaults. Running with gdb gives:- Starting program: /cygdrive/c/Program Files/Bitcoin/daemon/bitcoind Program received signal SIGSEGV, Segmentation fault. |
msvcrt.dll is File version: 7.0.2600.5512, md5 355edbb4d412b01f1740c17e3f50fa00 |
It may be that the new version of mingw that is used to compile the release no longer properly supports XP. Version 0.12.x is compiled in a Ubuntu 14.04 VM instead of 12.04. Someone enterprising could try to cross-compile 0.12 on Ubuntu 12.04 and see if that improves things. |
I compiled 0.12.0 on win 7 using mingw4.9 and qt 5.3.2. it got the same problem on Win XP(also crashed at msvcrt.dll).But after using "-listenonion=0" ,it works quite well excpet shutting down(not always).So I guess it maybe not because of cross compile in Ubuntu 14.04. Could anyone make further tests and fix it ? |
Can you get a proper backtrace? ('bt' in gdb) after a crash? Previous ones have only mentioned the topmost function, while what we need is to know where the crash originates in application code. |
I configured '--enable-debug' and compiled bitcoin-qt.exe on winXP directly, gdb with IDE(eclipse for c++),but failed to locate the additional source code,the result is : Thread #9 0 (Suspended : Signal : SIGSEGV:Segmentation fault)
I also tried "ollydbg", but still failed. It seems related to setlocal() function in msvcrt.dll. I don't know how to add conditional break point to stop before it crash wihie it's called too frequent |
That's unfortunate. Without knowing where the call comes from there is very little to do. These are some pointers when googling for crashes in that function, maybe useful to someone:
Note that the last item, Tor Browser Bundle's gitian has a workaround to link against
And it seems we link against msvcrt.dll as well, not msvcr100:
I don't have time to investigate this further, but maybe this helps someone. |
I am experiencing this exact same issue on my XP machine, if there is data I can provide from my setup that would be helpful in developing a fix for this I would like to help. |
Have you tried passing |
Tried it both in a .conf file and launched from the command line and it still crashed crashed crashed. Oh well, stuck with 0.11.2 I guess. |
There exists a bug in msvcrt.dll, setlocal() function. It crashed at the same stack as the above google results. so it can be solved by linking msvcrt100.dll or avoid this bug like previous releases. |
@coinyBit2 Everyone who does gitian builds build all of the versions. There is no one person who just does Windows stuff or is in charge of windows builds. Since this problem is limited to XP, which has reached its EOL, no one has fixed it yet and it has not been deemed a high priority by the other developers because the issue is not seen in any other version of windows. |
I don't think it's the same bug as tor's:
|
There is no one interested in maintaining Windows XP support, you're on your own here. At some point the price of buying new hardware/software is lower than the value of the time you'll spend on getting something to work. |
You can also try a lightweight OS instead, as suggested in #7681 (comment) |
With information found by lamar8 and following discussion in the QT project forum it seems to be a QT library issue only. Indeed, bitcoin-qt.exe of Bitcoin Core 0.11.2 is linked with QT 5.5.0 and it works properly on Windows XP SP3 32bit. Besides the workaround there is a real fix in the QT code. Take a look at their already fixed QTBUG-50188 bug report: I don't know which QT version is used in Bitcoin Core 0.12.x but updating it to the latest or making a custom QT build with -no-directwrite flag should fix the bitcoin-qt.exe crashes on Windows XP. Please use one of the above solutions. Windows XP is not dead yet! |
@tzofeolam Interesting, thanks for figuring that out! Bumping Qt on master has to happen before the 0.13 release (and if it really fixes this issue it could be be backported to 0.12) but as the latest official release of Qt is 5.6.0, that could only make it worse in that regard. In any case it'd be useful to experiment with that. |
Well that is good news for us XP users, now I can only hope this gets incorporated into the next version because I am not savvy enough to employ any of those Qt fixes myself. |
I cannot make the 0.12.x series run on Windows XP SP3, nor will 0.11.2 run for long. The best luck I've had is with 0.10.3, but it keeps crashing at length with a message about "Expression: hashPrevBlock == view.GetBestBlock()". This is reported to be in main.cpp, line 1660. |
Closing this issue: No one with an interest in bringing back XP compatibility showed enough initiative in the time frame available. Windows XP is no longer supported as of 0.13: CompatibilityMicrosoft ended support for Windows XP on April 8th, 2014, In addition to that, with 0.12.x there have been varied reports of Bitcoin Core We do not have time nor resources to provide support for an OS that is No attempt is made to prevent installing or running the software on Windows XP, |
Here's a debug.log fragment:
http://pastebin.com/u14vGP5z
Sometimes the app don't crash and running normally. But mostly not.
Previous version (0.11.2) works fine.
The text was updated successfully, but these errors were encountered: