Thread: Sigil-2.0.0 Released
View Single Post
Old 09-28-2023, 05:54 PM   #183
DNSB
Bibliophagist
DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.
 
DNSB's Avatar
 
Posts: 47,076
Karma: 169815798
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos
Quote:
Originally Posted by KevinH View Post
Perhaps it is a platform specific bug? Would someone on Windows or Linux please try recreating Vanguard3000's MetaData Editor crash on their platform just in case.
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.
Attached Files
File Type: txt Sigil_crash_windbg.txt (24.3 KB, 186 views)
Last edited by DNSB; 09-28-2023 at 06:18 PM.
DNSB is offline   Reply With Quote