Crash on Viewing Homepage (B9)

Upon viewing the homepage: The spinny thing spins for about 5 seconds and then crash. This crash has been reproduced about 5 times in a row.

Ever since getting B9, Logos 4 has been virtually unusable for me. I crash upon trying to open reading plan (may be related to reading plans being on homepage). I have had about 3 random crashes while reading that I cannot figure out what has happened. I haven't been able to go more than 5 minute without a crash.

I don't get the option to report it to Microsoft.

Find more posts tagged with

Performance

Comments

Bradley Grainger (Logos)

Upon viewing the homepage: The spinny thing spins for about 5 seconds and then crash. This crash has been reproduced about 5 times in a row.

This was caused by a combination of bad code in the home page, and bad tagging in the message it's trying to display from logos.com. I've fixed both now, but obviously you can't get the new home page code until Beta 10.

The problem may resolve itself tomorrow when the home page automatically refreshes. Until then, hold down the CTRL key at startup, check the "Use blank layout" checkbox, then click "Sign In" to prevent the home page automatically opening at startup.

Jason

Unsure if this is related but as I loaded L4 today I got a crash saying something about "this should link to a web page" or something like that. I did have to press the sign in button as I have updated my firewall and it was asking for me to verify the L4 access. Will try the hold control on opening and see if make a difference. Have to say L4Beta has been a killer on the data usage in last few days! [:)]

Log file attached.

7220.Logos4-startup crash.log

Bradley Grainger (Logos)

Log file attached.

The crash in the log file is a Beta 9 bug that has already been fixed in RC1. (The "this should link to a web page" message was not a crash, but a test of the "Alerts" system that was added recently.)

Ruben Gomez

Thanks for the tip, Bradley.

All of a sudden, when I tried to open Logos 4 this morning I kept
getting an error message saying that a problem has been detected and
the program must quit. I guess this is all related to the Homepage.

Still running beta 9 here, since I can't obviously update to RC1.

Should I wait or is there a fix already for this problem?

Thanks.

Ruben Gomez

Okay, forget my previous post. It is working now after updating.

Jacob Hantla

I just had this happen running RC1