Logos 4 crashes when trying to edit reading plan

It has never happened before this and I have edited my reading plans many before. Today, I tried to edit my 3 month reading plan and got an error message that Logos has stopped working and then it shut down. This happened several times, so I just created a new reading plan. That worked okay but I would like the editing to work as before

My version of the software is 4.2a SR-3 (4.21.5.0932). I am using Windows 7 SP1 on an ASUS laptop UL80V with4 mb RAM

Thanks

Find more posts tagged with

Comments

Graham Criddle

Hi Rainer - and welcome to the forums.

Assuming you still have the plan and are able to reproduce the crash when editing, would you be able to do so with diagnostic logging enabled and then post the logs to the forum? Please see http://wiki.logos.com/Diagnostic_Logging for details of how to do this.

This would enable people in the development team to try and determine what is happening.

Many thanks, Graham

Tobias Lampert

Rainer,

Please activate Diagnostic Logging and upload the log file the next time this happens.

Off topic: Are you German? I actually know some German people by name Mittelstädt, so I'm just curious.

Rainer Mittelstaedt

https://community.logos.com/discussion/comment/235941#Comment_235941

2043.Logos4.log

I attached the diagnostic log. Yes, I am German background, however born in Canada.

Tobias Lampert

https://community.logos.com/discussion/comment/235949#Comment_235949

Yes, I am German background, however born in Canada.

Thanks for letting me know - welcome to the forums, Rainer!

Graham Criddle

https://community.logos.com/discussion/comment/235949#Comment_235949

I attached the diagnostic log.

Thanks Rainer

Looks strange - as though Logos just stopped writing to the log virtually as soon as you tried to start the reading plan.

Hope someone more capable than I in log analysis can throw some light on this

Graham

Melissa Snyder

https://community.logos.com/discussion/comment/235949#Comment_235949

I attached the diagnostic log.

There's no crash data in the log. Was there a Logos4crash.txt created after the initial crash or subsequent crashes occurred?

Are you able to edit the new Reading Plan without a crash?

Rainer Mittelstaedt

https://community.logos.com/discussion/comment/235993#Comment_235993

Hi Melissa:

To my knowledge there was no Logos4crash.txt created.

I am able to create a new reading plan but not able to edit any of the reading plans I have. Every time I click on on "Edit" Logos a floating window flashes briefly and then Logos stops working.

Anything I need to do to generate Logos4crash.txt?

Thanks,

Rainer

Melissa Snyder

https://community.logos.com/discussion/comment/236003#Comment_236003

Hi Melissa:

To my knowledge there was no Logos4crash.txt created.

I am able to create a new reading plan but not able to edit any of the reading plans I have. Every time I click on on "Edit" Logos a floating window flashes briefly and then Logos stops working.

Anything I need to do to generate Logos4crash.txt?

Thanks,

Rainer

A Logos4crash.txt file isn't always generated. You might try reproducing the crash again with logging enabled, and after it crashes wait a minute to make sure the program is completely closed out. Don't restart it until you've copied the resulting Logos4.log and Logos4crash.txt (if available) and/or attached them to this thread. (Note: a Logos4crash.txt file can be created without logging enabled, but it is helpful to get the full logs by temporarily enable logging.)

Rainer Mittelstaedt

https://community.logos.com/discussion/comment/236026#Comment_236026

Hi Melissa:

Just wondering if there is any resolution to this issue. I've loaded up another diagnostic log file:

4617.Logos4.log

Logos 4 crashes no matter how I try to edit a Reading Plan--whether by clicking on "edit" on home page or going to File-->Open {any Reading plan}

I cannot even open an old plan to delete it.

Thanks

Rainer

OS: Windows 7 Home Premium service pack 1; System: Asus Notebook UL80VT Series; Intel Processor U7300 @ 1.30GHz 1.30 GHz; Memory 4.00GB; 64-bit; Vipre Anivirus Premium (Sunbelt Software)

Melissa Snyder

https://community.logos.com/discussion/comment/240374#Comment_240374

I will submit the new log to development. It still doesn't have any crash information, though. Does the program close on its own, or do you have to End Task on it in Task Manager?

Are you still able to create a new Reading Plan? If so, once that is created, does Logos 4 crash when you try to edit it?
If you right-click on a Reading Plan title under File | Open, and choose "Open in a new tab" (which opens it as a docked panel rather than a floating window) and then edit it, does the same thing occur?
Can you open other existing documents without problem?

Phil Mason

I am having the same issue with my reading plan iPhone.

As soon as I try to open the plan, it crashes.

Always been great....

What's up?

Rainer Mittelstaedt

https://community.logos.com/discussion/comment/240408#Comment_240408

Hi Melissa: Thanks for your response.

To answer your questions: the program closes and a window comes up that says "Logos Bible Sotfware has stopped working." then is say Window is is checking for a solution....then it changes to... "A problem caused the program to stop working correctly.Windows will close the program an notifyyou if a solution is available." [debug] [close program]

1. I am still able to create a new reading plan. When I try to edit it Logso still crashes.

2.If I right click on Reading Plan the same thing occurs whether I try to open as floating window or docked tab (although when I click on delete it does delete the Reading plan-I had not tried that earlier so thanks for pointing out the right click options)

3. I have no problem opening other documents.

Thanks.

Rainer

Melissa Snyder

https://community.logos.com/discussion/comment/240585#Comment_240585

To answer your questions: the program closes and a window comes up that says "Logos Bible Sotfware has stopped working." then is say Window is is checking for a solution....then it changes to... "A problem caused the program to stop working correctly.Windows will close the program an notifyyou if a solution is available." [debug] [close program]

1. I am still able to create a new reading plan. When I try to edit it Logso still crashes.

2.If I right click on Reading Plan the same thing occurs whether I try to open as floating window or docked tab (although when I click on delete it does delete the Reading plan-I had not tried that earlier so thanks for pointing out the right click options)

3. I have no problem opening other documents.

Thanks.

Thank you. We will update this thread when we have more information, or if we need any additional info from you.

Melissa Snyder

https://community.logos.com/discussion/comment/240585#Comment_240585

Rainer ~ Development is asking to get a crash dump since no crash log was generated. Please follow the steps on the wiki page and after zipping the resulting Logos4.dmp file, email it to Logos4feedback@logos.com. Thank you.

Edit: Sorry, I neglected to add the link to the wiki page: http://wiki.logos.com/ProcDump.

Rainer Mittelstaedt

https://community.logos.com/discussion/comment/240767#Comment_240767

Hi Melissa:

I followed the instructions with ProcDump application and everything worked fine until I did what causes the crash (i.e. tried to edit the Reading Plan. Logos shuts down and the command screen shows a line that "the process has exited." I cannot seem to find a logos4.dmp file.

I have tried this twice with the same result. Perhaps I am missing something.

Thanks

Rainer

Rainer Mittelstaedt

https://community.logos.com/discussion/comment/240789#Comment_240789

Okay, I tried the second option "Creating a Hang Dump." That seemed to work and I have now sent the file.

Rainer

Melissa Snyder

https://community.logos.com/discussion/comment/240789#Comment_240789

Hi Melissa:

I followed the instructions with ProcDump application and everything worked fine until I did what causes the crash (i.e. tried to edit the Reading Plan. Logos shuts down and the command screen shows a line that "the process has exited." I cannot seem to find a logos4.dmp file.

I have tried this twice with the same result. Perhaps I am missing something.

To locate the file, try typing logos4.dmp in the Search programs and files box on the Start Menu. If the file appears at the top of the menu, right-click on it and choose "Open file location." It should have been saved in the same directory into which you unzipped the procdump executable in step 1.

Melissa Snyder

https://community.logos.com/discussion/comment/240798#Comment_240798

Okay, I tried the second option "Creating a Hang Dump." That seemed to work and I have now sent the file.

Rainer

Our posts crossed paths. I'll submit the hang dump to development and see if that is sufficient.

Bradley Grainger (Logos)

https://community.logos.com/discussion/comment/240800#Comment_240800

I've started investigating the dump file and can see that the program is crashing inside the calendar/date picker control (a third-party control). I haven't been able to find anyone else on the Internet reporting a similar problem, so I'm not totally sure what might be causing it. I also haven't been able to reproduce it yet.

Are you using the "English (Canada)" date and time format (in "Region and Language" settings in Control Panel)?

Do you happen to recall if you have successfully edited any reading plans since Daylight Saving Time started?

Please post a screenshot of your Reading Plan before clicking the "Edit" link (i.e. what it looks like right before it crashes).

Rainer Mittelstaedt

https://community.logos.com/discussion/comment/240856#Comment_240856

Hi Bradley:

Thanks for looking into this.

I am using the English (Canada) date and time format but I seem to recall changing the short date format to yyyy-mm-dd. Last time I successfully edited my Reading Plans would have been at the beginning of this year. (Note: I have always used that date format).

Here is what it looks like just before I click Edit:

Immediately after clicking edit, it briefly shows the floating edit screen which disappears and then this appears:

.... followed by this:

I hope this helps

Rainer

Rainer Mittelstaedt

https://community.logos.com/discussion/comment/240885#Comment_240885

Hi Bradley:

I experimented a little based on what you said:

You mentioned the regional settings for time and date and I pointed out that my short date format was yyyy-mm-dd. I thought I might try something, so I changed the short date format setting to dd-mm-yyyy; then started Logos4 and tried to do a reading plan edit. Everything now worked as it should! I then went back to change the short date format to yyyy-mm-dd as before and tried an edit and it crashed again.

Conclusion: So it seems that Logos4 as it is now does not like my preferred yyyy-mm-dd short date format.

I don't edit my reading plans often and I can, as a work around, adjust the regional settings temporarily when I need to edit them. If there was an internal fix to Logos4 that would be of course better. I'd be interested to know if that can happen.

Thanks

Rainer

Rainer Mittelstaedt

https://community.logos.com/discussion/comment/240998#Comment_240998

Hi Bradley,

I experimented some more....

I also changed the long date format in the regional settings from MMMM-dd-yy to MMMM d, yyyy. I then tried the edit and it worked. When I then changed it back, Logos 4 crashed again while doing the edit.

Conclusion: Logos4 does not like yyyy-MM-dd and MMMM-dd-yy combination in date settings.

It seems to work with yyyy-MM-dd and MMMM d, yyyy which are settings I like, so for me the issue is now resolved. Thanks for pointing me in the right direction.

Rainer

Bradley Grainger (Logos)

https://community.logos.com/discussion/comment/241004#Comment_241004

Conclusion: Logos4 does not like yyyy-MM-dd and MMMM-dd-yy combination in date settings.

I can reproduce the crash with these instructions; thanks for your investigative work.

As mentioned earlier, the calendar/date picker control (which is crashing) is a third-party control, so we'll have to wait and see how quickly they can fix this once we report the problem to them.