Topic: 0.96.3992 with 0.15.1 (Win 10 X 64) may have become corrupted (Read 174 times)

I have certainly fallen into the trap of assuming Armory was hung and killing processes prematurely.

It is difficult because sometimes it DOES hang and then you are sitting there for hours not knowing what is going on.

It is certainly not my place to suggest adding anything to goatpigs plate, and I do not know what the investment or pitfalls might be, but perhaps a little more monitoring in the GUI where users were reassured that something is indeed happening might reduce the workload here.

Perhaps a one line text window in the GUI that would scroll the log file as it was written, but I am, of course, talking out my ass as I have no idea what that would entail.

Depends how much of the stack you are restarting. If it's everything (node, db, client), it's gonna take a couple minutes. If you just shut down the client but left the db and node running, restarting the client will basically be instant.

TY for the suggestions to delete the Armory Log and the db Log.  

Deleted the Armory Datebase folder.  Opened 0.15.1 and let it sync. Closed 0.15.1
performed a new load of 0.96.3992  

0.96.3992 with 0.15.1 is now loaded and sync'd.  

Experiment re Logout was successful, though somewhat slow.  
New open of 0.96.3992 was somewhat slow, but it did successfully open, sync (and remains open)

These are the respective logs at this standing.

Ar = https://pastebin.com/yR7GDgAa
db = https://pastebin.com/XSwkuT8c

Thank you for confirming all is fine, also any ideas on why this is now rather slow loading into the computer
(Are there any ideas re interference after the recent Windows forced update)

Thank you for your kind attention.  

Delete dbLog.txt, try again and post the file. Same with armorylog.txt.

These are the conditions:

Using a shared Win 10 x 64 computer dedicated to Armory with the local area friend.
Originally configured successfully June, July 2017 with 0.96.0.4 and Core 0.14.2
(to be prepared for Seg-Wit, and the August 1 hard fork).  

Over the past weekend an upgrade to 0.96.3992 with Core 0.15.1 had been successful after a number of attempts
(with TY to all in the forum for the excellent suggestions)  

Further experiments to open Armory and close Armory seemed successful, Armory remained open overnight.

It had been thought that Window's updates had been disabled, but there was a forced reboot of the computer
for a Windows upgrade.  Following the reboot, 0.96.3992 didn't open correctly and had to be forced into shutdown.  

Following the prior recommendations for install the Armory folder was deleted.  
0.15.1 database properly sync'd and then properly closed.  

Subsequent attempts to load 0.96.3992 now hang at the opening rounded rectangle.
Observation of "process manager" insdicates that bitcoind.exe and ArmoryQT.exe are engaged.
ArmorydB.exe appears, but is not active

These folders are the successive Armory logs.  The dBlog file has become circa 4.4 Gbyte and not practical to copy.

Four pastebin files in succession for the Armory Log
https://pastebin.com/rVK6bS8g
https://pastebin.com/v6hCEWJz
https://pastebin.com/TN8NGuZ0
https://pastebin.com/03c4Afff

Thank you for your advice and suggestions.  
I have a guess it may be necesssary to fully reload 0.15.1 from scratch on the dedicated Armory computer.

This is the computer intended for install of the added databases
and to separate BCH from the legacy BTC positions.  

There are two other computers used each of us - for our regular internet connections.  
Each of those computers has 0.96.3992 and 0.15.1 fully operational and non contaminated
Each respective On Line computer has a dedicated off line computer for signing transactions.

Thank you again for your help.