Crashing when closing program to install update

Gabe Powell
Gabe Powell Member Posts: 76 ✭✭
edited November 20 in English Forum

Every time a new Beta comes out, the install crashes right away, but then continues to work. I think what is actually crashing is closing the program in order to continue installing. Since I haven't been able to repeat this right away I didn't report it, but it happens with each new beta update. Just in case here are the logs.

 

6622.DigitalLibraryInstall.zip

Laptop: Windows 7 Professional x64, Intel Dual-Core, 2GB RAM, Radeon X1600

Home: Vista Ultimate x86,  AMD Quad-Core, 4GB RAM, GeForce 8400 GS 512MB

Work: Windows 7 x64, Intel Dual-Core, 8GB RAM, Radeon X1300/X1550

Tagged:

Comments

  • DominicM
    DominicM Member Posts: 2,995 ✭✭✭

    I can replicate this...

    Never Deprive Anyone of Hope.. It Might Be ALL They Have

  • Bryan Albert
    Bryan Albert Member, Logos Employee Posts: 92

    Gabe,

    Thank your for this valuable log file, it helps solve (hopefully) a mystery. So this problem happens with every update, on any of your three machines? Do you remember exactly how you initiate the update? There are three or four ways you could initiate an update: the first way is via the splash screen. If Logos 4 isn't running when the Indexer finishes downloading the update, and you subsequently launch Logos 4, it will show a message box that says, "Updates are ready to be installed. Do you want to install them now? (Recommended.)" If you chose Yes, you should not get the crash. This probably isn't you, since you suspect that it's shutting down Logos 4 that's failing. The second way is to choose "Install Update" from the Indexer icon's menu, available only if the balloon tip has already gone away. The third way is by clicking on the balloon tip on the Indexer icon (in the System Notification Area at the right end of the Task Bar). I think you could also click or double-click on the Indexer icon, or right-click it when the balloon is visible, and it would start the update as well. So... any idea how you usually do it?

    I'm suspecting that pre-Beta 6 versions of the Indexer can launch multiple instances of the Logos4Setup.exe under certain circumstances. If you had a copy of the logos4indexer.log file written when you installed the update (but before Logos 4 restarted and overwrote the log file--you'd have to copy it before Windows Installer was finished installing the update), it might confirm that theory. If, on a future update, you do get the error, please click the Cancel button on the Windows Installer dialog in order to pause the installation, then find the logos4indexer.log file and set it aside. I'd like to see it!

    So the problem here is that there are two instances of Logos4Setup.exe running when there should only be one. This can cause a crash of one of them, like you're experiencing, or an error dialog saying, "The installation of ... did not succeed." The other instance goes on to complete the update. This problem should be fixed with the Beta 6 version of the Indexer, so now that your Indexer has been updated to beta 6, the next update should not exhibit the problem. If it does, please let us know!

    Thanks!

    Bryan

     

  • Gabe Powell
    Gabe Powell Member Posts: 76 ✭✭

    The two main ways I have installed updates is by 1) clicking on the balloon, and 2) right-click the system tray icon and selecting Install. For the first three or so updates I just clicked the balloon, and then I started right-clicking the system tray icon.

    If it crashed at the next update I'll cancel the installer and upload the file right away.

    Laptop: Windows 7 Professional x64, Intel Dual-Core, 2GB RAM, Radeon X1600

    Home: Vista Ultimate x86,  AMD Quad-Core, 4GB RAM, GeForce 8400 GS 512MB

    Work: Windows 7 x64, Intel Dual-Core, 8GB RAM, Radeon X1300/X1550