Beta 5 Download crashes Also

http://community.logos.com/forums/t/15968.aspx

The above was posted on the Logos 4 forum when I attempted to download the upgrade from 4.0b SR-1 to 4.0b SR-2.

As I could not "move up" with the "calm-cool" stable version (see details above) I figured I might as well go back to the 'exciting" beta's.

No luck yet. The beta (or the 1,000 MB download "froze" everything. My memory usage of the Logos program actually reached 1.96 GB on a 2 GB machine. When the mouse would no longer move I re-booted .

After re-booting the download resumed. I hope I will be able to successfully re-boot in order to instal it.

Here are all of my 5 logs from after the download crash.

8547.DigitalLibraryInstall.zip

Find more posts tagged with

Comments

SteveF

Woes continue:

[I only have a 32 bit machine - I cannot install more memory.]

This time Logos ran the memory usage up to 1,290,388K before the dreaded M$ error message appeared.[It continues to grow during Error reporting - 1,371,604K with total used at 2.1GB].

By then the 1,000MB download had ended and the indexing had begun to estimate (began at a few minutes but was soon up over 2 hrs).

Something is "leaking very badly" for this program to "run-away" recklessly like this.

[There is an extra frustration level here because of the hard drive crash two weeks ago - logos 4 (Method 2) seemed to re-install the program flawlessly -- but I am having a very difficult time trying to get it to update anything without continual crashes. I have NOT added any new resources -- only logos central's own (apparently) updated files]

All the logs while M$ error message happening and Logos 4 still on the screen:

5732.Logos4.zip

M$ Error reporting still seems to take 7-15 minutes on this machine. Since this beta process began back in September, no one has yet ventured a reason why the logos error reports take so long on some of our machines. Most/all other program error reports go by so quickly there is hardly time to close the requester]..

As I wait for the M$ error report to finish the index estimate continues to "grow." Now is up to 5 hrs. - now 7 hours

Not having enough expertise to read logs, I'm assuming the problem lies in the installer (but that does not make sense as 'we" have been installing now for over 6 months.)

I'm afraid the whole machine will again freeze up. I am posting this before the Error report finishes.

SteveF

https://community.logos.com/discussion/comment/121173#Comment_121173

error report finally ended at 11:42(probably the longest one ever - over 30 minutes?)

Indexing estimate up to 11 hours

logs

4263.DigitalLibraryInstall.zip

Dave Hooton

https://community.logos.com/discussion/comment/121173#Comment_121173

All the logs while M$ error message happening and Logos 4 still on the screen:

These logs are exactly the same as your previous set and they relate to 4.0b. The Crash log dates from 6 days ago. But it shows you have only 6 GB of temp space on your system C: drive (plenty on your installation drive) - so I would look to free some more space there. You should kill the M$ report and post fresh logs.

EDIT: whilst our messages crossed, your latest 4623 logs are still the same ones as before!

SteveF

https://community.logos.com/discussion/comment/121188#Comment_121188

But it shows you have only 6 GB of temp space on your system C: drive (plenty on your installation drive)

Thank you for looking at these Dave.

But this really concerns me.

There should be lots of room on this drive. It is about 250 GB which when formatted reports capacity of 233GB. I thought system temp "drawers" or "files" etc just expanded as needed? I don't understand. This one drive contains the Windows OS and all of the Program Files. There are no "partitions." As of now it has 141GB free.

As to the logs, I will try again to hold down the ctrl key next time I re-start.

Which I have been trying to do.

SteveF

https://community.logos.com/discussion/comment/121204#Comment_121204

6 GB of temp space

I'm trying to find where to change this.

I've found "Virtual Memory" and where to adjust Memory Space allocated to System Restore but I don't think that what you are referring to.

[It is getting late at night here, and my mind has drawn a blank -- where do I change "temp space on my system C drive"?

Any suggestion as to suggested size (once i find it) based on 250 GB size of HD?

Dave Hooton

https://community.logos.com/discussion/comment/121204#Comment_121204

There should be lots of room on this drive. It is about 250 GB which when formatted reports capacity of 233GB. I thought system temp "drawers" or "files" etc just expanded as needed? I don't understand. This one drive contains the Windows OS and all of the Program Files. There are no "partitions." As of now it has 141GB free.

Sorry Steve I should have said free space (which is available for
temporary files, etc). The crash log from 15 April showed only 6 GB free on C: drive. If it now has 141 GB free then there is no issue.

As to the logs, I will try again to hold down the ctrl key next time I re-start.

Just enable permanent logging - Diagnostic Logging then you will not have to remember the Ctrl key!

SteveF

https://community.logos.com/discussion/comment/121229#Comment_121229

Thanks for clarifying.

I do not know how that old log survived.

From that crash date, it goes back to last week when I had loaded Logos and Windows on a 40GB drive while trying to resurrect my large drive after it's crash.

Diagnostic Permanent logging has been turned back on.

As to the indexing, at midnight it was down to just 2 hours remaining. I got up this morning and after it ran all night it now says 9 hours remain, so I have no idea what went on (or didn't) during the entire night.

I guess there is no use sending any logs untill this has finished indexing. And "if" it does and starts "fine", they still may show nothing?

Steve

Dave Hooton

https://community.logos.com/discussion/comment/121313#Comment_121313

As to the indexing, at midnight it was down to just 2 hours remaining. I got up this morning and after it ran all night it now says 9 hours remain, so I have no idea what went on (or didn't) during the entire night.

Because of the 2 indexes in 4.0b/c and the fact it does the Bible Index before the Library Index you will find the 2 hours came from the former whilst the 9 hours came after starting on the Library Index!

I guess there is no use sending any logs untill this has finished indexing. And "if" it does and starts "fine", they still may show nothing?

You sneak a look at the Indexer log and look for occurrences of BibleIndex which should be followed by occurrences of LibraryIndex and you will get a better idea of progress.

[it's my bed time now]

SteveF

https://community.logos.com/discussion/comment/121320#Comment_121320

[it's my bed time now]

Thans DAve for this all night "other-side-of-the-world" help!