View Single Post
Old 09-28-2023, 06:29 PM   #186
KevinH
Sigil Developer
KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.
 
Posts: 8,893
Karma: 6120478
Join Date: Nov 2009
Device: many
Interestingly, your debuuger log shows the crash deep in QtCore and not actually in Sigil.

Quote:
2e40.49e4): Access violation - code c0000005 (first chance)
First chance exceptions are reported before any exception handling.
This exception may be expected and handled.
Qt6Core!QBitArray::QBitArray+0x1e:
00007ffc`095d67de f041ff00 lock inc dword ptr [r8] ds:baadf00d`baadf00d=????????
0:000> g
(2e40.49e4): Access violation - code c0000005 (!!! second chance !!!)
Qt6Core!QBitArray::QBitArray+0x1e:
00007ffc`095d67de f041ff00 lock inc dword ptr [r8] ds:baadf00d`baadf00d=????????
0:000> g
(2e40.49e4): Access violation - code c0000005 (first chance)
First chance exceptions are reported before any exception handling.
This exception may be expected and handled.
Qt6Core!QBitArray::QBitArray+0x1e:
00007ffc`095d67de f041ff00 lock inc dword ptr [r8] ds:baadf00d`baadf00d=????????
That is probably why is works just fine on MacOS but crashes on Windows.

I will try this is my Linux box when I get it setup tomorrow to see if it crashes too. Running a debugger there is much easier. Hopefully it will give us some idea of what is actually causing the crash so I can try and prevent it.

Thanks!

Kevin

Quote:
Originally Posted by DNSB View Post
I tried removing all elements visible in the Metadata Editor and under Windows 11 using Sigil 2.0.1 build time 2023.09.04 21:17:31 UTC, and got a crash as soon as I clicked on OK.

I've attached the Windows Event Viewer crash report and WinDbg output as a text file.

Looking at @BetterRed's message, I tried with an empty ePub 3 and when I removed all three elements (Language, Title and Date Modified), crash time. As long as one element is left, no crash. OTOH, removing all elements is a bit odd since AFAIR, title, language and identifier are mandatory elements and removing them gives an invalid ePub.
KevinH is offline   Reply With Quote