nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

crash while using highlighter tool

Levi Penner

Every time I use the highlighter tool, after a few uses, the logos crashes. 7673.Logos Log Files.zip

Find more posts tagged with

Comments

Philana R. Crouch

Every time I use the highlighter tool, after a few uses, the logos crashes. 7673.Logos Log Files.zip

Eli,

It looks like logging isn't turned on, there are no crashes recorded in your logs. Please follow the instructions to enable logging found in my signature. Reproduce the issue, and zip the logs folder before you restart Logos, then upload them here. Also please provide step to reproduce. What highlighting style are you using? What resource and where in the resource are you trying to highlight?

If you could provide this information it will help.

Blessings,

Philana

Levi Penner

https://community.logos.com/discussion/comment/859243#Comment_859243

4162.Oct 19 Log Files.zip

Dave Hooton

https://community.logos.com/discussion/comment/860372#Comment_860372

It would be useful to see Window Event Viewer logs.

Levi Penner

https://community.logos.com/discussion/comment/860483#Comment_860483

There were no errors at the time of the crash. I'm not sure if it helps, but I did find an error at another time stamp and have copied the content in the general tab.

Faulting application name: LogosCEF.exe, version: 1.4.0.0, time stamp: 0x57743e90
Faulting module name: libcef.dll, version: 3.2704.1431.0, time stamp: 0x57644782
Exception code: 0xc0000005
Fault offset: 0x0000000000e6520b
Faulting process id: 0x5e8
Faulting application start time: 0x01d22a30a21d1d4c
Faulting application path: C:\Users\Jarvis\AppData\Local\Logos\System\LogosCEF.exe
Faulting module path: C:\Users\Jarvis\AppData\Local\Logos\System\libcef.dll
Report Id: 8e3a378b-da6d-4cfc-85bf-b9a4050c8bba
Faulting package full name:

Levi Penner

https://community.logos.com/discussion/comment/860533#Comment_860533

I made the crash happen again this morning. Here are the logs and the corresponding windows event.

5710.Oct 20 Log files.zip

Faulting application name: LogosCEF.exe, version: 1.4.0.0, time stamp: 0x57743e90
Faulting module name: libcef.dll, version: 3.2704.1431.0, time stamp: 0x57644782
Exception code: 0xc0000005
Fault offset: 0x00000000003af916
Faulting process id: 0x2788
Faulting application start time: 0x01d22add5c5d9edc
Faulting application path: C:\Users\Jarvis\AppData\Local\Logos\System\LogosCEF.exe
Faulting module path: C:\Users\Jarvis\AppData\Local\Logos\System\libcef.dll
Report Id: b8602671-ef10-43e1-a39f-3f37733def7c
Faulting package full name:
Faulting package-relative application ID:

Levi Penner

https://community.logos.com/discussion/comment/860536#Comment_860536

This error occurred about one minute before the previous error.

Faulting application name: Logos.exe, version: 6.14.0.65, time stamp: 0x57e167ea
Faulting module name: ltc_game64-116096.dll, version: 1.0.0.1, time stamp: 0x57cf505f
Exception code: 0xc00000fd
Fault offset: 0x000000000000319b
Faulting process id: 0x12d0
Faulting application start time: 0x01d22add25cede8c
Faulting application path: C:\Users\Jarvis\AppData\Local\Logos\System\Logos.exe
Faulting module path: C:\PROGRA~2\RAPTRI~1\PlaysTV\ltc_game64-116096.dll
Report Id: 32a17e7e-fa89-42c2-bd87-0fbca7766255
Faulting package full name:
Faulting package-relative application ID:

Philana R. Crouch

Every time I use the highlighter tool, after a few uses, the logos crashes. 7673.Logos Log Files.zip

Levi,

I would recommend reaching out to Customer Support.

Thomas Ball

https://community.logos.com/discussion/comment/860540#Comment_860540

Hi Levi,

Solution 4 here should help you: https://www.logos.com/support/logos6/windows/crash

Levi Penner

https://community.logos.com/discussion/comment/860602#Comment_860602

Thanks, I have an AMD graphics processor and it appears the solution from the link you sent has solved my problem. Thanks again.