Sigil Crashing on 2nd monitor

[KevinH]

Okay I repeated those tests but this time with the second monitor set on the left of the primary monitor, and it all worked exactly as expected on macOS.

So I can not recreate what you are seeing. It is most probably Windows specific or specific to your setup somehow.

So I have posted a debug Windows build here:

https://github.com/kevinhendricks/Bu...OnMac/releases

Please grab:

Sigil-master-screen-debug-Win-Setup.exe

To use it you need to set the SIGIL_DEBUG_LOGFILE environment variable to point to a text file on your Desktop (or someplace you can easily access).

Then run the working setup with the secondary screen on the right.

Then copy the resulting debug log file to a new file called "working_log.txt" and empty it in prep for the version that crashes (or just change the name of the file in your SIGIL_DEBUG_LOGFILE environment variable).

Then run the version with the second screen on the left, that causes the crash.

Copy the rename the resulting debug log file to "crash_log.txt" then please zip up and post "crash_log.txt" and "working_log.txt" here so that we can see it and look to see if anything obviously wrong is being detected.

Thanks!

[Turtle91]

OK.
Attached are the log files. I added another log to show the working, about to fail, and failed situation.

working_log.txt is a Sigil instance used and closed normally

about_to_crash_log.txt is a Sigil instance where it worked normally, but I set it up in a known failure mode eg. I closed it while it was on the secondary monitor

crash_log.txt is a Sigil instance that failed to open

edit: ooops, I think I may have forgotten to clear the log file between the working_log, and the about_to_crash_log... The first 166 lines of the about_to_crash_log are the same as the working_log.

Do you want me to redo?

[Turtle91]

FYI

I was again able to recover Sigil by:
- putting the #1 monitor to the left in Display Settings
- opened Sigil
- closed Sigil
- changed Display settings back to #1 on the right
- reopened Sigil normally

[KevinH]

There was no crash activity associated with the crashlog. The Window is never properly moved to the primary screen as it should have been according to qt docs and it stays invisible (just like whenI turn off the power but do not disconnect the extra monitor).

Have you fully disconnected your second monitor or just turned it off?

Does Windows Display Settings, have a "Gather Windows" button?

Could Sigil NOT have "crashed" but be just sitting there idle ?

[KevinH]

Also, does this issue only happen when you Maximize the Window? What happens if you try the same thing and do not maximize.

[Turtle91]

Originally Posted by KevinH

There was no crash activity associated with the crashlog. The Window is never properly moved to the primary screen as it should have been according to qt docs and it stays invisible (just like when I turn off the power but do not disconnect the extra monitor).
Have you fully disconnected your second monitor or just turned it off?

I did not turn off or disconnect either monitor. I simply dragged the Sigil window to the 2nd monitor and closed it. When I attempted to reopen Sigil it crashes. When I go to Display settings and move the #1 monitor to the left of the #2 monitor, Sigil then opens fine.

Originally Posted by KevinH

Does Windows Display Settings, have a "Gather Windows" button?

Not by that name...but I think you may be referring to the "Extend Displays" function (see attached image) that creates one large desktop where the mouse flows from the edge of one display to the edge of the other continuously via the orientation shown in the graphic. In the image you would move your mouse from the right edge of monitor 2 and it would show up on the left edge of monitor 1.

I usually have these monitors set to "Extend these Display"

Originally Posted by KevinH

Could Sigil NOT have "crashed" but be just sitting there idle ?

Here are a couple links to video showing what I term a "crash"..."Sigil is not responding", and how I get it to recover.

Showing Sigil Crash:
https://www.dropbox.com/s/3mi9gyt8lz...Crash.MOV?dl=0

Showing Sigil Recovery:
https://www.dropbox.com/s/bkrz2exp91...cover.MOV?dl=0

[Turtle91]

Originally Posted by KevinH

Also, does this issue only happen when you Maximize the Window? What happens if you try the same thing and do not maximize.

Hoooooboy....now ya gone an dunit...


I did the exact same procedure as mentioned above to get Sigil to crash except I left Sigil as a non-maximized window....with the exact same results.

However...
When I tried my recovery procedure of moving the #1 monitor from the right to the left of the #2 monitor...it did NOT recover. It actually stayed on the #2 monitor and remained in its unresponsive state.
I was able to get this one to recover by going into display settings and selecting "Show only on 1"...which has the same effect as disconnecting the 2nd monitor.


edit: Added links to video showing crash/recovery in windowed (non-maximized) mode

Crash 2:
https://www.dropbox.com/s/x1pa5nkyo5...rash2.MOV?dl=0

Recovery 2:
https://www.dropbox.com/s/j20phhnrtd...over2.MOV?dl=0

[Turtle91]

Just to make me feel better about myself....

Here is another set of logs, properly cleared between attempts, showing:
- Sigil working
- Sigil moved to 2nd monitor - about to crash
- Sigil crashed on the 2nd monitor
- Sigil after recovery by turning off the 2nd monitor using "Show only on 1" in Display Settings

[theducks]

Scaled 150%
FWIW I was running Calibre (5.99.8 W10x64) on my main, scaled 125% and the child windows (MDE) always open off from where I closed them.
It may be something to do with the 0,0 (relative) point being Multiplied by the Scale factor

[DNSB]

I gave it a try and I can't duplicate Turtle91's issue on either of my dual monitor setups. I tried swapping monitors, changing which monitor was the main display, powering off or disconnecting a monitor, etc.

On one setup, there is an Intel UHD driver for one monitor and a NVidia driver for the second while the other setup uses the NVidia driver for both monitors. CPU is an Intel i7, memory is 32GB, OS is Win 11 Pro.

Are there any items in Windows Event viewer about the time that Sigil shows the issue.

[KevinH]

Okay, from comparing the crash logs to the good logs, there appears to be a missing Activation of the newly opened Sigil MainWindow. This activation happens right near the bottom of main.cpp.

The docs says that Windows can ignore this activation if for any reason it is in the middle of running a different process (Windows does not allow any interruptions).

So for some reason something else runs on your system in one configuration that does not in the other configuration. From the videos it appears that both your monitors are ASUS.

The ASUS Sound Studio 2 is a known program that interferes with Qt programs.

Are you absolutely positive that you are not running ASUS Sound Studio?

I can try to add a timer to try the activation again after a short delay. That might help.

Also please try rebooting into safe mode, with extensions off and see if the same strange issue still happens.

[Turtle91]

Originally Posted by DNSB

Are there any items in Windows Event viewer about the time that Sigil shows the issue.

I cleared the Event logs and caused Sigil to crash again. Event Viewer showed these:

Application:Error

The program Sigil.exe version 1.9.2.0 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Security and Maintenance control panel.
 Process ID: 7ec4
 Start Time: 01d8536afc9e15e9
 Termination Time: 5
 Application Path: C:\Program Files\Sigil\Sigil.exe
 Report Id: 49911ea7-3cf8-4c56-8b77-fd99669595e6
 Faulting package full name: 
 Faulting package-relative application ID: 
 Hang type: Cross-thread

Application:Information

Fault bucket 1787373574412397971, type 5
Event Name: AppHangB1
Response: Not available
Cab Id: 0

Problem signature:
P1: Sigil.exe
P2: 1.9.2.0
P3: 625d8677
P4: 32f2
P5: 134217736
P6: 
P7: 
P8: 
P9: 
P10: 

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.14056f97-afdf-4d2f-9684-eff4f6ce94e6.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.6cde5013-32c4-4e7c-8ced-049f9aa5b91b.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.14953a53-a5b7-4153-90ce-fff526bc7fa7.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.5538b5d2-a19b-4b1b-a9f8-08d3f9b228b8.tmp.txt
\\?\C:\Users\Dion\AppData\Local\Temp\WER.e5e8b62e-751b-4941-abf9-9407e916a2ff.tmp.appcompat.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppHang_Sigil.exe_dc701d3a10e35344fc4e1772bfe674612821da68_75f27853_cc9f8618-1d2a-43d2-b140-c4f4f98b1d55

Analysis symbol: 
Rechecking for solution: 0
Report Id: 49911ea7-3cf8-4c56-8b77-fd99669595e6
Report Status: 268435456
Hashed bucket: cc053fc4f9c7577f28ce06cbc7c56d93

[Turtle91]

Originally Posted by KevinH

The ASUS Sound Studio 2 is a known program that interferes with Qt programs.

Are you absolutely positive that you are not running ASUS Sound Studio?

Well....with Windows you can never be truly positive, 100%, no way no how...

But.... I haven't installed Sound Studio, it's not in my list of applications, it doesn't show up in Task Manager, and device manager only shows this under sound, video and game controllers:
- NVIDIA High Definition Audio
- NVIDIA Virtual Audio Device (Wave Extensible) (WDM)
- Realtek(R) Audio
- Sonic Studio Virtual Mixer

sooo, I'll just say I'm confident it is not installed.

Originally Posted by KevinH

Also please try rebooting into safe mode, withe tensionsoff and see if the same strange issue still happens.

I rebooted into Safe Mode (not sure what 'tensions off' means) and it only allowed 1 monitor...wouldn't even detect a second monitor...so I'm not sure that is a valid test??

[Turtle91]

Originally Posted by theducks

Scaled 150%
FWIW I was running Calibre (5.99.8 W10x64) on my main, scaled 125% and the child windows (MDE) always open off from where I closed them.
It may be something to do with the 0,0 (relative) point being Multiplied by the Scale factor

I used the "recommended" scale as suggested in the Display Settings window. I honestly haven't researched why it would be recommended over 100%???

I reran the crash/recovery procedure with everything set at 100% scale and it was the same result... I have included the logs from that test run here if it helps.

I was also thinking that I do use the windows zoom function quite regularly (ctrl+mouse wheel) (it's quite frustrating how publishers keep making their websites smaller and blurrier as I get older...we should start a protest ) and THAT may have effected these results...

However, I tested after resetting the zoom and it had the same results.

[KevinH]

Meant to have written "extensions off".

BTW, I think "Sound Studio" was an typo. The problem software is called "Sonic Studio".

I saw this on the QtBug report:

Uninstalling Sonic Studio 2 resolved the issue.

here:

https://bugreports.qt.io/browse/QTBUG-94216

https://bugreports.qt.io/browse/QTBUG-94217

So please try uninstalling your Sonic Studio Virtual Mixer and let us know if the problem goes away.