JohnAustinDev / xulsword

Automatically exported from code.google.com/p/xulsword
17 stars 6 forks source link

Error dialog upon launching application, and application remains empty #242

Closed DavidHaslam closed 7 years ago

DavidHaslam commented 7 years ago

I've not run the app for several months, so there've been some Windows Updates meanwhile.

Today, when I launched the app, the flash window did not close automatically and the following error dialog appeared for the first time in my experience.

screenshot 2017-01-25 12 08 37

I'm using Windows 7 x64 Home Premium Edition, fully up to date.

I have MK 3.12 installed (2016-02-19).

I also have Xiphos installed and recently installed the JSword based STEP Bible from Tyndale House.

After I clicked OK, the app itself appeared to be empty !!!

screenshot 2017-01-25 12 14 05

and the Help About | More was also blank.

screenshot 2017-01-25 12 15 59

In the TaskBar there's a thumbnail for a xulsword-temporary-hidden-window.

Didn't we see this a long time ago under Windows XP ?

DavidHaslam commented 7 years ago

As a check, I'm now installing MK 3.13 using the file MK_Setup(WINNT_x86_64-msvc)-3.13.exe that I dowloaded on 2016-03-21.

After installation, when the app was launched, the same thing occurred, apart from the minor difference in line number for the error.

screenshot 2017-01-25 12 29 00

DavidHaslam commented 7 years ago

I just downloaded and installed MK 3.14 using the file MK_Setup(WINNT_x86-msvc)-3.14.exe

The same thing occurred, except that the dialog appeared twice, and no longer gives any details.

screenshot 2017-01-25 12 46 55

The app has become unusable on my PC.

JohnAustinDev commented 7 years ago

Maybe this is problem caused by an anti virus program, or file permissions? Uninstall MK. Then manually remove any remaining MK files from your user profile by searching there for the folders /IBT/MK and entirely delete them all. Then reinstall MK 3.14 and try again. If there is an unhandled exception (error) it should ask you if you want to report it, and you should say yes.

DavidHaslam commented 7 years ago

File permissions shouldn't have changed.

I'm still using Microsoft Security Essentials as the AV program. I was already using this last time MK was working OK.

I also have MalWareBytes installed, but not the Premium version. I could eaisly disable this in Startup using Piriform CCleaner.

C:\Users\David\AppData\Roaming\IBT\MK\Profiles contains five profiles and one resources folder.

I have 66 modules installed in the latter. Is it safe to try your instructions without removing these resources?

DavidHaslam commented 7 years ago

I first stopped MalWareBytes. Then I deleted the five profiles (see above), but leaving the resources folder in place. Then I uninstalled MK successfully. Then I installed MK 3.14 again. It created a new profile, just as you described. After installation finished, and MK was opened, I got the same error message.

screenshot 2017-01-29 17 34 50

It did NOT ask me if I wanted to report it!

Please advise further.

DavidHaslam commented 7 years ago

The path C:\Users\David\AppData\Roaming\IBT\MK\Profiles\mwd1g468.default\datareporting contains a file called aborted-session-ping

I have zipped it in order to upload it here. It may contains some clues, but it's not something I understand.

aborted-session-ping.zip

JohnAustinDev commented 7 years ago

I haven't seen this problem before, and the aborted-session-ping suggest a hard crash of a Mozilla module. My best guess at this point is still interference from anti-virus or something. Security programs are constantly updating and changing, so it could be due to a changed security program, or operating system permission or other setting, rather than xulsword. (?)

You were fine to leave the resources directory and delete the rest. But you can try moving the resources directory somewhere else to save it, and then wiping out Roaming/IBT/MK entirely. There are also quickstart files stored by xulrunner that might be hanging around. So search for all IBT/MK directories below your /users/ (even hidden ones), and delete them as well, before reinstalling MK.

If you have a ConsoleLog.txt file in your MK/profile directory please upload that as it would be most helpful (if there is one- but the crash may prevent its writing).

DavidHaslam commented 7 years ago

This is what I did today:

Not yet run the program. Will report on that in next comment.

DavidHaslam commented 7 years ago

After running MK, the same error message appeared again (twice). In the TaskBar the thumbnail for a xulsword-temporary-hidden-window appeared transiently. A profile had been created: C:\Users\David\AppData\Roaming\IBT\MK\Profiles\hz8afaat.default The main program opened but appeared empty with three windows. See screenshot.

screenshot 2017-02-02 10 17 20

Selecting Windows | 1 Window did nothing. No resources were available to display.

The file C:\Users\David\AppData\Roaming\IBT\MK\Profiles\hz8afaat.default\consoleLog.txt was empty (zero bytes).

DavidHaslam commented 7 years ago

Ah! But upon closing the program, the same file was updated. Hereby attached.

consoleLog.txt

The 17 modules this records as dropping have nothing to do with MK. These are actually in my default Sword path, as used by Xiphos.

C:\Users\David\AppData\Roaming\Sword

I should add that they are by no means the only modules installed there.

DavidHaslam commented 7 years ago

Observing the first reported error in consoleLog.txt - I just looked in C:\Program Files (x86)\IBT\MK\xulrunner There was no such file as chrome.manifest

DavidHaslam commented 7 years ago

Observing other contents of the file, I couldn't help wondering why MK needs to do anything with Telemetry.

Line 59 reads:

[JavaScript Error: "1486030496132 Toolkit.Telemetry ERROR TelemetryStorage::loadAbortedSessionPing - error removing ping: PingReadError JS Stack trace: PingReadError@TelemetryStorage.jsm:80:15 < TelemetryStorageImpl.loadPingFile<@TelemetryStorage.jsm:1440:13" {file: "resource://gre/modules/Log.jsm" line: 749}]

JohnAustinDev commented 7 years ago

Thank you for including ConsoleLog.txt, that was very helpful. MK does look in your default Sword path for modules (just like Xiphos does). One or more of these modules is causing the problem. I see there is a module named: "ACF 2007". MK does not expect modules with spaces in their module code name for instance. When did this become allowable? This could be the culprit...

DavidHaslam commented 7 years ago

ACF2007 is not one from CrossWire or any of the other repositories listed in our MRL.

That Portuguese Bible module was recently (2017-01-19) downloaded from Siriarah.

I have just edited my copy of the conf file to remove the space and make the DataPath lowercase.

[ACF2007]
DataPath=./modules/texts/rawtext/acf2007/

I also left a comment in his comments page that the conf file requires correcting.

Xiphos had no difficulties displaying it. It's not that a space has become allowed. Rather perhaps it's that some front-ends are more forgiving than others.

Even so, this wasn't the first error listed in ConsoleLog.txt, was it? It can't account for the missing chrome.manifest, can it?

I will try opening MK again now that I've made the correction.

JohnAustinDev commented 7 years ago

Much of what is reported in ConsoleLog.txt is inconsequential, including the chrome.manifest error (Mozilla code looks for this file in many places and eventually finds it).

Typically, look for "JavaScript Error"s reported in chrome://xulsword files

DavidHaslam commented 7 years ago

Not yet tried to open MK again.

First I needed to tweak five modules from STEP Bible for which [ModName] contained a hyphen. As only valid characters are the PCRE class [A-Za-z0-9_] this was a sensible precaution. I have also advised the STEP development team leader accordingly.

Will try again later today.

DavidHaslam commented 7 years ago

Tried MK again after those tweaks to various modules.

Got further this time. The xulsword-temporary-hidden-window appeared transiently again.

The following error message also appeared twice when I opened the program.

screenshot 2017-02-03 15 56 20

However, the main app window appeared, with the first several module tabs.

screenshot 2017-02-03 16 17 57

FIO: Module ABU = American Bible Union New Testament (hence blank for Gen.1)

I tried a few tab clicks and eventually got one displayed.

screenshot 2017-02-03 16 20 07

But now observe the repeated set of tabs after the half way point!

Unable to consistently select another module after I reached this point. Sometimes it works, sometimes not. Some controls work but not correctly. I just ended up with this weird window layout.

screenshot 2017-02-03 16 23 54

After closing the program, here's the new consoleLog.txt file:

consoleLog.txt

Given that at least some progress has been made by making corrections to installed modules, I am now wondering which other modules might be causing all this remaining grief.

DavidHaslam commented 7 years ago

Any advice before my next try would be helpful.

JohnAustinDev commented 7 years ago

So it does appear to be the experimental or non-standard modules which are causing the problems. I would like to make MK handle these instances more gracefully. I would suggest saving all your C:\Users\David\AppData\Roaming\Sword modules somewhere else, and then deleting those modules. Then install particular modules one at a time so you know which one(s) cause problems, and report which modules those are. I will probably need access to those modules to insure all issues are dealt with. Are the offending modules available in a standard SWORD repository? If so, this is much higher priority.

DavidHaslam commented 7 years ago

Whenever I install a new module or make one myself, it's always in the normal Sword path.

The xulsword modules that I had earlier times installed from IBT were in the resources folder, the one that I moved to somewhere innocuous two days ago. That was not moved back yesterday.

Rather than moving all the modules, it would be simpler to temporarily move merely the most recent conf files away from the mods.d folder. This could be done in chunks, using the successive approximation method to home in to the largest set of modules that allows MK to work without errors.

Front-ends don't care about extra folders in the ztext folder if there's no configured DataPath pointing to them.

I think we may only have to consider modules made or installed since a year ago.

The possibility remains that eliminating some modules doesn't fix the error. But we shall see.

DavidHaslam commented 7 years ago

OK - further progress. I found on Saturday that my tweaks to some of the invalid modules from Tyndale STEP were incomplete, in that I'd not renamed the module folders in ztext. I fixed those yesterday.

I just found time now to open MK 3.14 again.

This time there were no error messages.

screenshot 2017-02-07 16 52 48

All is not yet well, but I should now close this issue and create a new issue for the fresh symptoms.