4.6beta 3 Crash on Startup (Not related to Handouts!): Error ID: 5844 / stylePath is not in the cor

This crash does not appear to relate to handouts - i followed the instructions given for that error, have not handouts, and it still crashes.

The crash log text is refering to problems with stylepath, Highlighting and VisualMarkups and VisualFilters.

Error ID: 5844

Error detail: FormatException: stylePath is not in the correct format.

Full logs:1768.Logos4_6a beta3.zip

Indexing appears to be carrying on fine while the app crashes around it.

Find more posts tagged with

Comments

Simon’s Brother

Indexing completed but still unable to use Logos as it simply crashes with the same error.

Fred Chapman

https://community.logos.com/discussion/comment/400929#Comment_400929

Ity looks to me like a visual filter is creating a problem. Are you trying to start with a blank layout? What happens if you rename your L4 documents folder?

Bradley Grainger (Logos)

The crash is happening when your local index of documents is rebuilt (two minutes after startup). It's caused by a Visual Filter, but unfortunately the error doesn't identify which one.

One possible workaround is to start the application, open the File menu, and delete any new visual filters (at the top of the File menu); they may be the ones causing the problem.

Simon’s Brother

https://community.logos.com/discussion/comment/401068#Comment_401068

The crash is happening when your local index of documents is rebuilt (two minutes after startup). It's caused by a Visual Filter, but unfortunately the error doesn't identify which one.

One possible workaround is to start the application, open the File menu, and delete any new visual filters (at the top of the File menu); they may be the ones causing the problem.

I tried deleting most recent visual filter's, a couple of them actually and the same crash kept occurring. Also tried renaming visual filters folder but this did not fix anything as it just re-downloaded the same visual filters from the server. In the end I simply deleted all of my visual filters and re-sync'd so I had a clean slate with no visual filters and all seems to be working fine. Not to worried about loosing the existing visual filters. I tend to use them for specific situations, rather than as permanent documents. I've rarely taken a hit when beta testing and nothing like some other's have experienced so have no issues loosing my visual filters at this point. I could have continued working through them one by one deleting and restarting, and ending up find it was the last one I deleted.

Maybe Logos 5 code could improve the error message output to identify the documents (not just visual filters) that cause these errors so it makes it easier for end uses and Logos support to resolve these issues - it won't always be ok to loose your user created documents - just so happens it was in this instance not a big issue for me.