alerque
commented
4 years ago Have you tried upgrading to 4.2.1? Is was that what you meant to type instead of "4.1.2"?
Open zrlaszlo opened 4 years ago
alerque
commented
4 years ago Have you tried upgrading to 4.2.1? Is was that what you meant to type instead of "4.1.2"?
zrlaszlo
commented
4 years ago Sorry for the typo, I meant 4.2.1, the latest build. Before I was running the build prior to 4.2.1 (can't remember the version number). My problems started with that one. I upgraded to the newest build, 4.2.1 and I the problem persists. Currently the program is unusable in my context.
karlkleinpaste
commented
4 years ago i don't know what to tell you about this. on the one win10 machine (real hardware) that i've got, it also shows having ...931 and ...799 installed, yet xiphos starts and runs immediately, no hesitation at all. are there any other recent differences to account for?
zrlaszlo
commented
4 years ago I updated some system drivers such as chipset and network adapter drivers. There were no other changes made to the system as far as I know. This afternoon I uninstalled Xiphos completely and reinstalled it. It does the same as described above. Still looking for a solution...
ildar
commented
4 years ago Running in console may show you something
zrlaszlo
commented
4 years ago Running in console may show you something
Do you mean this? (see picture)
The outcome is the same as before.
ildar
commented
4 years ago Ain't no Linux 😞
ildar
commented
4 years ago Actually system journal Apps should have something
karlkleinpaste
commented
4 years ago no, "console mode" means a build with the console still enabled. normally, windows graphical applications are built so as to silence the console entirely. pick up this: http://ftp.xiphos.org/sword/xiphos/xiphos-4.2.1.2-win64.exe after install, start it from a cmd window. you may learn something useful.
zrlaszlo
commented
4 years ago I installed and ran the program above. The error mesage reads:
Error loading plugin: 'C:\Program Files\Crosswire\xiphos\lib\enchant\libenchant_myspell.dll': The specified module could not be found.
What is strange to me is that the file xiphos claims not to find is still there – see second attachment. There is a similar file in the \bin directory, should I replace the missing file from there?
zrlaszlo
commented
4 years ago Actually I did. Now the program does not return any kind of error message whatsoever, but sill crashes towards the end of the splash screen. Where to look for to find a clue?
ildar
commented
4 years ago the last thing comes to my mind is running with gdb or maybe with strace analog: https://stackoverflow.com/questions/3847745/systrace-for-windows Maybe Karl has better ideas.
zrlaszlo
commented
4 years ago I took a look today in the MS EventViewer and the following erorrs tied to every Xiphos startup (the part down to the "Fault offset…" etc. line is always the same, from that point on it may vary). Can someone point out the problem? Thank you! Here is the error report: Faulting application name: xiphos.exe, version: 0.0.0.0, time stamp: 0x00000000 Faulting module name: libwebkitgtk-1.0-0.dll, version: 0.0.0.0, time stamp: 0x00000000 Exception code: 0xc0000005 Fault offset: 0x000000000085a38f Faulting process ID: 0x190c Faulting application start time: 0x01d62ce6fc0bbfa2 Faulting application path: C:\Program Files (x86)\CrossWire\Xiphos\bin\xiphos.exe Faulting module path: C:\Program Files (x86)\CrossWire\Xiphos\bin\libwebkitgtk-1.0-0.dll Report ID: 4a53ba18-b24b-46d8-9db7-a3bf9675fd7c Faulting package full name: Faulting package-relative application ID:
karlkleinpaste
commented
4 years ago a bit of googling tells me that Exception code: 0xc0000005 is an "access violation," or what we in linux-land would call a segfault. probably some null pointer was accessed, and faceplant.
the idea that webkit is causing this is ... extraordinarily suspect. WK has been our display driver (it is responsible for all the HTML-driven formatting of all the textual display widgets) for some years now, and particularly in windows since v3.1.4 or so.
i cringe to suggest this, but... there is a gdb (debugger) in xiphos' bin directory. invoke xiphos indirectly using gdb. that means, instead of "xiphos", run "gdb xiphos.exe" (you may have to give it a complete path to reach the xiphos.exe binary; i don't know), and after you get its self-announcement and a "(gdb)" prompt, say simply "r" for run. it will do its thing for a while and (we presume) crash, at which point you will get an announcement by gdb of what went wrong, and a new prompt. at that point, say "bt" (backtrace) and save what it tells you, but not more than the top 15 or so frames. (they're numbered.) the process is still alive but suspended as it approaches death; just kill it with "k" and quit out of gdb.
gdb's backtrace is likely the end of the line for the help we can provide.
ultimately, this may be a problem of some corrupted module in your Sword area. that could plausibly lead to such a drastic formatting failure that WK would choke. but i doubt it.
zrlaszlo
commented
4 years ago Dear Karl, I followed your procedure, it was quite easy. Below you find the entire output, I hope it will shed some light on what is going on. Thank you for your concern!
(gdb) r Starting program: c:\Program Files\Crosswire\xiphos\bin\xiphos.exe [New Thread 4060.0x4640] [New Thread 4060.0x2318] [New Thread 4060.0x15d0] [New Thread 4060.0x5208] [New Thread 4060.0x4a3c] [New Thread 4060.0x4118] [New Thread 4060.0x532c] [New Thread 4060.0x2324] [New Thread 4060.0x3304] [New Thread 4060.0x1b54] [New Thread 4060.0x26d8] [New Thread 4060.0x42e8] [New Thread 4060.0x2010] [New Thread 4060.0x3a90] [New Thread 4060.0x4808] [New Thread 4060.0x480c] [New Thread 4060.0x4b00]
Thread 1 received signal SIGSEGV, Segmentation fault. 0x00000000017aa58f in WebCore::RenderStyle::computedLineHeight(WebCore::RenderView*) const () from c:\Program Files\Crosswire\xiphos\bin\libwebkitgtk-1.0-0.dll (gdb) bt
from c:\Program Files\Crosswire\xiphos\bin\libwebkitgtk-1.0-0.dll
() from c:\Program Files\Crosswire\xiphos\bin\libwebkitgtk-1.0-0.dllfrom c:\Program Files\Crosswire\xiphos\bin\libwebkitgtk-1.0-0.dll
from c:\Program Files\Crosswire\xiphos\bin\libwebkitgtk-1.0-0.dll
from c:\Program Files\Crosswire\xiphos\bin\libwebkitgtk-1.0-0.dll
from c:\Program Files\Crosswire\xiphos\bin\libwebkitgtk-1.0-0.dll
from c:\Program Files\Crosswire\xiphos\bin\libwebkitgtk-1.0-0.dll
from c:\Program Files\Crosswire\xiphos\bin\libwebkitgtk-1.0-0.dll
from c:\Program Files\Crosswire\xiphos\bin\libwebkitgtk-1.0-0.dll
from c:\Program Files\Crosswire\xiphos\bin\libwebkitgtk-1.0-0.dll
from c:\Program Files\Crosswire\xiphos\bin\libwebkitgtk-1.0-0.dll
from c:\Program Files\Crosswire\xiphos\bin\libwebkitgtk-1.0-0.dll
from c:\Program Files\Crosswire\xiphos\bin\libwebkitgtk-1.0-0.dll
from c:\Program Files\Crosswire\xiphos\bin\libwebkitgtk-1.0-0.dll
from c:\Program Files\Crosswire\xiphos\bin\libwebkitgtk-1.0-0.dll
from c:\Program Files\Crosswire\xiphos\bin\libwebkitgtk-1.0-0.dll
from c:\Program Files\Crosswire\xiphos\bin\libwebkitgtk-1.0-0.dll
from c:\Program Files\Crosswire\xiphos\bin\libwebkitgtk-1.0-0.dll
from c:\Program Files\Crosswire\xiphos\bin\libwebkitgtk-1.0-0.dll
from c:\Program Files\Crosswire\xiphos\bin\libwebkitgtk-1.0-0.dll
from c:\Program Files\Crosswire\xiphos\bin\libwebkitgtk-1.0-0.dll
from c:\Program Files\Crosswire\xiphos\bin\libwebkitgtk-1.0-0.dll
from c:\Program Files\Crosswire\xiphos\bin\libwebkitgtk-1.0-0.dll
from c:\Program Files\Crosswire\xiphos\bin\libwebkitgtk-1.0-0.dll
from c:\Program Files\Crosswire\xiphos\bin\libwebkitgtk-1.0-0.dll
from c:\Program Files\Crosswire\xiphos\bin\libwebkitgtk-1.0-0.dll
from c:\Program Files\Crosswire\xiphos\bin\libwebkitgtk-1.0-0.dll
---Type
zrlaszlo
commented
4 years ago This may also be helpful...
from c:\Program Files\Crosswire\xiphos\bin\libwebkitgtk-1.0-0.dll
from c:\Program Files\Crosswire\xiphos\bin\libwebkitgtk-1.0-0.dll
from c:\Program Files\Crosswire\xiphos\bin\libwebkitgtk-1.0-0.dll
from c:\Program Files\Crosswire\xiphos\bin\libwebkitgtk-1.0-0.dll
from c:\Program Files\Crosswire\xiphos\bin\libwebkitgtk-1.0-0.dll
from c:\Program Files\Crosswire\xiphos\bin\libwebkitgtk-1.0-0.dll
from c:\Program Files\Crosswire\xiphos\bin\libwebkitgtk-1.0-0.dll
from c:\Program Files\Crosswire\xiphos\bin\libglib-2.0-0.dll
Backtrace stopped: previous frame inner to this frame (corrupt stack?)
zrlaszlo
commented
4 years ago Some more news: I removed all files from the folder C:\Users\zrlas\AppData\Roaming\Sword and launched Xiphos. It launched without error and started the Module Manager. I added a number of modules, restarted Xiphos but same problem: crashed during splash screen. I repeated the process you described, and here is the backtrace log:
(gdb) r Starting program: c:\Program Files\Crosswire\xiphos\bin\xiphos.exe [New Thread 2680.0x2cc4] [New Thread 2680.0x2568] [New Thread 2680.0x268c] [New Thread 2680.0x2684] [New Thread 2680.0x1c5c] [New Thread 2680.0x26b8] [New Thread 2680.0x26bc] [New Thread 2680.0x504] [New Thread 2680.0x580] [New Thread 2680.0xbcc] [New Thread 2680.0x318] [New Thread 2680.0x314] [New Thread 2680.0x480] [New Thread 2680.0x610] [New Thread 2680.0x364] [New Thread 2680.0x57c] [New Thread 2680.0x894]
Thread 1 received signal SIGSEGV, Segmentation fault. 0x000000000169a58f in WebCore::RenderStyle::computedLineHeight(WebCore::RenderView*) const () from c:\Program Files\Crosswire\xiphos\bin\libwebkitgtk-1.0-0.dll (gdb) bt
from c:\Program Files\Crosswire\xiphos\bin\libwebkitgtk-1.0-0.dll
from c:\Program Files\Crosswire\xiphos\bin\libwebkitgtk-1.0-0.dll
from c:\Program Files\Crosswire\xiphos\bin\libwebkitgtk-1.0-0.dll
from c:\Program Files\Crosswire\xiphos\bin\libwebkitgtk-1.0-0.dll
() from c:\Program Files\Crosswire\xiphos\bin\libwebkitgtk-1.0-0.dllfrom c:\Program Files\Crosswire\xiphos\bin\libwebkitgtk-1.0-0.dll
from c:\Program Files\Crosswire\xiphos\bin\libwebkitgtk-1.0-0.dll
from c:\Program Files\Crosswire\xiphos\bin\libwebkitgtk-1.0-0.dll
---Type
from c:\Program Files\Crosswire\xiphos\bin\libwebkitgtk-1.0-0.dll
from c:\Program Files\Crosswire\xiphos\bin\libwebkitgtk-1.0-0.dll
from c:\Program Files\Crosswire\xiphos\bin\libwebkitgtk-1.0-0.dll
from c:\Program Files\Crosswire\xiphos\bin\libwebkitgtk-1.0-0.dll
from c:\Program Files\Crosswire\xiphos\bin\libwebkitgtk-1.0-0.dll
from c:\Program Files\Crosswire\xiphos\bin\libwebkitgtk-1.0-0.dll
from c:\Program Files\Crosswire\xiphos\bin\libwebkitgtk-1.0-0.dll
from c:\Program Files\Crosswire\xiphos\bin\libwebkitgtk-1.0-0.dll
from c:\Program Files\Crosswire\xiphos\bin\libwebkitgtk-1.0-0.dll
from c:\Program Files\Crosswire\xiphos\bin\libwebkitgtk-1.0-0.dll
from c:\Program Files\Crosswire\xiphos\bin\libwebkitgtk-1.0-0.dll
from c:\Program Files\Crosswire\xiphos\bin\libwebkitgtk-1.0-0.dll
from c:\Program Files\Crosswire\xiphos\bin\libwebkitgtk-1.0-0.dll
---Type
karlkleinpaste
commented
4 years ago this sequence is insane.
44 0x000000000043da60 in xiphos!on_edit_activate2 () 45 0x00000000004394d4 in xiphos!gui_menu_prayerlist_popup () 46 0x000000000045455e in xiphos!on_edit_activate2 () 47 0x00000000004013c5 in ?? ()
on_edit_activate2 is part of the process of beginning to edit an existing prayerlist/journal. gui_menu_prayerlist_popup is the beginning of offering a new prayerlist/journal. neither of these events is plausibly happening at start, nor do they mutually reference each other, that one could call the other which would call back.
i'm afraid that what this means is that at some point the backtrace is invalid. that can be caused by someone using a pointer so badly that it trashes the stack, for example. other possibilities exist.
bottom line is that i know no more now than i did 20 minutes ago. this is a fundamental "cannot reproduce" problem. you're the only person showing this problem, and you had it under both 4.1.0 and 4.2.1. this can tell me only that it is your system, not xiphos, that is causing a problem. but on the win10 boxes i have, fully updated, xiphos starts just fine.
i don't know what else to offer. i don't have any other diagnostic suggestions.
ildar
commented
4 years ago Joining this guessing game: do other applications crash at times? Maybe Windows BSOD? if so, this is hardware problem.
zrlaszlo
commented
4 years ago Windows is running just fine without any issues. What I have noticed is that between the two backtraces there is a difference: in the second one there is no reference to the prayerlist Karl mentioned. Ï will try to roll back the display driver, other option does not come to my mind concerning my system.
loveofthetruth
commented
3 years ago I'm having the same problem with Xiphos 4.2.1 on windows 10 64 bit on a Lenovo ThinkPad e580 laptop, it crashes on startup after the splash screen closes and the program window comes up, it then disappears, I also used gdp to debug and this is what I got: C:\Program Files\CrossWire\Xiphos\bin>gdb xiphos.exe GNU gdb (GDB) 8.0 Copyright (C) 2017 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-w64-mingw32". Type "show configuration" for configuration details. For bug reporting instructions, please see: http://www.gnu.org/software/gdb/bugs/. Find the GDB manual and other documentation resources online at: http://www.gnu.org/software/gdb/documentation/. For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from xiphos.exe...(no debugging symbols found)...done. (gdb) r Starting program: C:\Program Files\CrossWire\Xiphos\bin\xiphos.exe [New Thread 3896.0xf28] [New Thread 3896.0x353c] [New Thread 3896.0x1b88] [New Thread 3896.0x4788] [New Thread 3896.0x18b8] [New Thread 3896.0x38a4] [New Thread 3896.0x24ac] [New Thread 3896.0x1a74] [New Thread 3896.0x2654] [New Thread 3896.0x419c] [New Thread 3896.0x3290] [New Thread 3896.0x19d8] [New Thread 3896.0x3288] [New Thread 3896.0x24a8] [New Thread 3896.0x3ce4] [New Thread 3896.0x1210] [New Thread 3896.0x3c2c] [New Thread 3896.0x191c]
Thread 1 received signal SIGSEGV, Segmentation fault. 0x00000000017da58f in WebCore::RenderStyle::computedLineHeight(WebCore::RenderView*) const () from C:\Program Files\CrossWire\Xiphos\bin\libwebkitgtk-1.0-0.dll
I have had the same problem on windows 7 32 on an older laptop with an older version of Xiphos but I can't remember the version, according to this debug output it looks like a webkit issue, how is it possible that I have had the issue on two different machines with two different versions of Xiphos, I have not had much look with Xiphos on Windows 7 or 10. I doubt it is a hardware issue since it has happened on two different machines with two different version of Xiphos, to me it looks like either webkit or gtk is the culprit.
Xiphos has been working on my system flawlessly for quite a while (Win10 Pro x64, Ryzen 7). After having installed yesterday Microsoft updates KB4556799 and KB4552931 Xiphos started crashing on launch: the splash screen appears, then the program window behind, but as soon as the launch screen is done, they both (launch screen and program window) disappear into thin air whether I run the program as and administrator or not. I upgraded to Xiphos version 4.1.2 x64, the problem remains. Xiphos is my favourite Bible software, what should I do? Many thanks!