Screen going white and Qlog not reponding

[n5im]

hello,
I am running Qlog ver, 0,5,1,1 on a windows 10 box. Occasionally the screen will go completely white and Qlog stops responding and then closes. Is this a known issue? This happens every day.
Thanks for any help. It's a GREAT program, it's just this one annoying issue.

Thanks from Texas de N5IM

[aa5sh]

I have not heard of that but it sounds like something is causing it to freeze up. How long does it normally take before it freezes? You can try to start a debugging log you can add here or send to me to look at. The directions are in the wiki https://github.com/foldynl/QLog/wiki/Debug-Log-Level on how to start it up and where it saves on Windows. If it takes a while this debug file could get quite large but really would be the only way to tell what is going on.

73
Michael, AA5SH

[n5im]

Michael,

Thanks for the tip on the debugging file. I am now running the program to collect the file, and will share it as soon as I have it.

73
Bill N5IM

[n5im]

Hello Michael,   I have captured a debug log file, but it is 1.2 gb and I don't have a program can handle such a large taxt file. And I wouldn't know what I'm looking for. any ideas?   73 de Bill N5IMVidor, TX   Sent: Saturday, July 18, 2026 at 7:22 PM From: "Michael Morgan" ***@***.***> To: foldynl/QLog ***@***.***> CC: n5im ***@***.***>,Author ***@***.***> Subject: Re: [foldynl/QLog] Screen going white and Qlog not reponding (Discussion #1103)   I have not heard of that but it sounds like something is causing it to freeze up. How long does it normally take before it freezes? You can try to start a debugging log you can add here or send to me to look at. The directions are in the wiki https://github.com/foldynl/QLog/wiki/Debug-Log-Level on how to start it up and where it saves on Windows. If it takes a while this debug file could get quite large but really would be the only way to tell what is going on. 73 Michael, AA5SH — Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS and Android. Download it today! You are receiving this because you authored the thread.Message ID: ***@***.***>

[aa5sh]

You can try to run something like this in a command prompt. Just change the path to the actual right path of the debug log file. IT should display the last 1000 lines of the file. Maybe we can see what it was doing when it is freezing. powershell -command "Get-Content 'C:\logs\biglog.txt' -Tail 1000” If not you can download vscode from Microsoft. It may open that size of file and you can go the bottom and send the last couple hundred lines. I was afraid it was going to be a huge file size it is was so infrequently doing it.

…

On Jul 21, 2026, at 1:56 PM, n5im ***@***.***> wrote: Hello Michael, I have captured a debug log file, but it is 1.2 gb and I don't have a program can handle such a large taxt file. And I wouldn't know what I'm looking for. any ideas? 73 de Bill N5IMVidor, TX Sent: Saturday, July 18, 2026 at 7:22 PM From: "Michael Morgan" ***@***.***> To: foldynl/QLog ***@***.***> CC: n5im ***@***.***>,Author ***@***.***> Subject: Re: [foldynl/QLog] Screen going white and Qlog not reponding (Discussion #1103) I have not heard of that but it sounds like something is causing it to freeze up. How long does it normally take before it freezes? You can try to start a debugging log you can add here or send to me to look at. The directions are in the wiki https://github.com/foldynl/QLog/wiki/Debug-Log-Level on how to start it up and where it saves on Windows. If it takes a while this debug file could get quite large but really would be the only way to tell what is going on. 73 Michael, AA5SH — Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS and Android. Download it today! You are receiving this because you authored the thread.Message ID: ***@***.***> — Reply to this email directly, view it on GitHub <#1103?email_source=notifications&email_token=AUEEMXSRPK7MFU2D5B7ONHT5F64EXA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNZXGIYTQMJXUZZGKYLTN5XKOY3PNVWWK3TUUVSXMZLOOSWGM33PORSXEX3DNRUWG2Y#discussioncomment-17721817>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AUEEMXVMJNTMOQMF7ALHOY35F64EXAVCNFSNUABIKJSXA33TNF2G64TZHMZTQNZUG4ZDCMJXHNCGS43DOVZXG2LPNY5TCMBUGUZTCMBXUF3AE>. Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/AUEEMXRS2Q2NQZMDP5ET2KL5F64EXA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNZXGIYTQMJXUZZGKYLTN5XKOY3PNVWWK3TUUVSXMZLOOSVGM33PORSXEX3JN5ZQ> and Android <https://github.com/notifications/mobile/android/AUEEMXVCR5H7CLITBIUWDZT5F64EXA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNZXGIYTQMJXUZZGKYLTN5XKOY3PNVWWK3TUUVSXMZLOOSXGM33PORSXEX3BNZSHE33JMQ>. Download it today! You are receiving this because you commented.

[n5im]

tried the command and got error:
'Get-Content' is not recognized as an internal or external command,
operable program or batch file.

[n5im]

Well, I I opened the file in vscode and went to the bottom, but I don't know what I'm looking at means.

[aa5sh]

If you want to grab the last bit of the log and save as a text file then save here or email it to me I’ll take a look and see if I can see anything.

…

On Tue, Jul 21, 2026 at 4:17 PM n5im ***@***.***> wrote: Well, I I opened the file in vscode and went to the bottom, but I don't know what I'm looking at means. — Reply to this email directly, view it on GitHub <#1103?email_source=notifications&email_token=AUEEMXUOGHQY7AHWBSQ3UHT5F7MWLA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNZXGIZTIMBWUZZGKYLTN5XKOY3PNVWWK3TUUVSXMZLOOSWGM33PORSXEX3DNRUWG2Y#discussioncomment-17723406>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AUEEMXQWTBEYIXZZ7SIDAFT5F7MWLAVCNFSNUABIKJSXA33TNF2G64TZHMZTQNZUG4ZDCMJXHNCGS43DOVZXG2LPNY5TCMBUGUZTCMBXUF3AE> . Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/AUEEMXRLHT5WISAQN44K4ET5F7MWLA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNZXGIZTIMBWUZZGKYLTN5XKOY3PNVWWK3TUUVSXMZLOOSVGM33PORSXEX3JN5ZQ> and Android <https://github.com/notifications/mobile/android/AUEEMXTSH25H4SRNWQV7DEL5F7MWLA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNZXGIZTIMBWUZZGKYLTN5XKOY3PNVWWK3TUUVSXMZLOOSXGM33PORSXEX3BNZSHE33JMQ>. Download it today! You are receiving this because you commented.Message ID: ***@***.***>

[n5im]

I didn't know how much to save, but here it is
QLog_debug_N5IM.txt

[aa5sh]

Looks like it may be something with your graphics card or system. Not sure if your computer may be going to sleep or something . But you can try starting QLog like this from a command window. You would need to cd to program files then QLog directory first. I’m Not at home the give all the exact commands for that but I can in a little while. set QSG_RHI_BACKEND=software set QT_QUICK_BACKEND=software QLog.exe

…

On Tue, Jul 21, 2026 at 6:26 PM n5im ***@***.***> wrote: I didn't know how much to save, but here it is QLog_debug_N5IM.txt <https://github.com/user-attachments/files/30246650/QLog_debug_N5IM.txt> — Reply to this email directly, view it on GitHub <#1103?email_source=notifications&email_token=AUEEMXUZ5LLNMEPCJIQ7K535F733PA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNZXGI2DKOBSUZZGKYLTN5XKOY3PNVWWK3TUUVSXMZLOOSWGM33PORSXEX3DNRUWG2Y#discussioncomment-17724582>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AUEEMXVBYQHZ5XEPE3GPDO35F733PAVCNFSNUABIKJSXA33TNF2G64TZHMZTQNZUG4ZDCMJXHNCGS43DOVZXG2LPNY5TCMBUGUZTCMBXUF3AE> . Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/AUEEMXQPJY6GIKC5DKGYOY35F733PA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNZXGI2DKOBSUZZGKYLTN5XKOY3PNVWWK3TUUVSXMZLOOSVGM33PORSXEX3JN5ZQ> and Android <https://github.com/notifications/mobile/android/AUEEMXQGBWR2QK53NCYPDW35F733PA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNZXGI2DKOBSUZZGKYLTN5XKOY3PNVWWK3TUUVSXMZLOOSXGM33PORSXEX3BNZSHE33JMQ>. Download it today! You are receiving this because you commented.Message ID: ***@***.***>

[foldynl]

Yes, as @aa5sh wrote, there are warnings about GPU in your log. Try what @aa5sh wrote, or you can also try running QLog with these seetting - executed in the directory, where QLog is installed

set "QTWEBENGINE_CHROMIUM_FLAGS=--disable-gpu --disable-software-rasterizer" && QLog.exe

If one of them helps, then you have a graphics card that is not supported by QLog and these switches say that everything should be rendered by the CPU.

[n5im]

So, guys, I think the commands that AA5SH gave solved the problem of the screen going white! Thanks very much for your help. Now QLog is taking a LONG time loading the profile image, but I guess I'll have to live with that.
:

I am running a DELL laptop...attaching the system info