Sigil 2.8.6 crashes on Windows11 when adding a cover to a large EPUB3 - Page 2

DNSB · Today, 09:42 PM

Edited my message to reflect testing the fixed epub.

DiapDealer · Today, 09:44 PM

Quote:

Originally Posted by KevinH

My bad, that test epub was missing almost all of its spine. That was the point of that test epub!

Phew! I thought I was losing my mind!

I can confirm that there's no crash, and no spine jumbling, using the fixed 2500files epub on a fairly tired Windows 10 laptop using Sigil 2.8.6. It takes a bit, but I honestly thought it would be slower.

DiapDealer · Today, 09:52 PM

We still probably need to find out how massive the OP's epub really is. It could contain thousands of images which would increase the size of the manifest that lxml would need to parse.

KevinH · Today, 10:09 PM

Perhaps the OP is using/trying with an epub2, which will take much longer and invoke python more often due to looking for the guide entry for cover (if you have 2500 files the opf will be parsed 2500 times looking to see if that resource has the cover semantic set).

I can certainly speed that up for the next release by extracting the entire guide once and storing it in a hashtable for fast lookups.

Luckily parsing an epub3 nav for landmark codes is much much faster as it uses gumbo and not python lxml.

But the OP specified epub3 in the thread title, so ...

rinsay · Today, 10:23 PM

I tried the same EPUB file on another Windows 11 PC, and Sigil 2.8.6 worked fine. The PC that’s having issues has 32GB of memory, so I don’t think it’s a case of insufficient memory. Maybe something wrong with my PC, but I’m not sure exactly what it is.

Today, 10:09 PM	#19
KevinH Sigil Developer Posts: 10,206 Karma: 7640000 Join Date: Nov 2009 Device: many	Perhaps the OP is using/trying with an epub2, which will take much longer and invoke python more often due to looking for the guide entry for cover (if you have 2500 files the opf will be parsed 2500 times looking to see if that resource has the cover semantic set). I can certainly speed that up for the next release by extracting the entire guide once and storing it in a hashtable for fast lookups. Luckily parsing an epub3 nav for landmark codes is much much faster as it uses gumbo and not python lxml. But the OP specified epub3 in the thread title, so ... Last edited by KevinH; Today at 10:18 PM.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
[Plugin] ePub3-itizer - epub3 output plugin for Sigil	KevinH	Plugins	458	10-04-2026 11:07 AM
Two problems in Sigil 2.7.0 in Windows11	philja	Sigil	22	02-06-2026 09:32 AM
Adding Images Crashes Sigil	Paredon	Sigil	7	10-19-2023 01:34 AM
Epub crashes on Sigil for Mac, OK on Sigil for PC	crystamichelle	Sigil	6	08-14-2013 03:52 PM
Sigil adding blank page after cover image	ebookn00b	Sigil	32	06-20-2013 02:44 PM

Today, 09:42 PM	#16
DNSB Bibliophagist Posts: 55,727 Karma: 182544312 Join Date: Jul 2010 Location: Vancouver Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos	Edited my message to reflect testing the fixed epub.

Today, 09:52 PM	#18
DiapDealer Grand Sorcerer Posts: 29,925 Karma: 212736631 Join Date: Jan 2010 Device: Nexus 7, Kindle Fire HD	We still probably need to find out how massive the OP's epub really is. It could contain thousands of images which would increase the size of the manifest that lxml would need to parse.

Today, 10:23 PM	#20
rinsay Junior Member Posts: 2 Karma: 10 Join Date: Nov 2026 Device: iReader Ocean5 Pro	I tried the same EPUB file on another Windows 11 PC, and Sigil 2.8.6 worked fine. The PC that’s having issues has 32GB of memory, so I don’t think it’s a case of insufficient memory. Maybe something wrong with my PC, but I’m not sure exactly what it is.

Advert

Advert