Repeated crash - Page 2

DiapDealer · 11-07-2017, 12:51 PM

I can't get it to crash on my Windows machine either. Is there something other than making sure the html toc (which is listed in the guide as the toc) is open in Code View before generating the html toc? Do I need a specific test case epub?

My Windows machine is using Qt5.6.2 (same Qt the official Sigil release uses) and my Linux machine is using Qt5.9.2.

KevinH · 11-07-2017, 01:27 PM

I deleted the test case but perhaps the op will pm you with it as he did me. All I had to do was open that ePub, and then open the current html toc in Codeview. By default I have the pane for the toc ncx open on the left and preview pane open on the right.

I only tested by removing the guide entry (all worked) and by manually closing HTML toc (again all worked).

If I didn't do either and tried to create HTML toc, the crash happened 100% of the time

DiapDealer · 11-07-2017, 01:32 PM

There must be something about that specific toc or epub, then. Because I haven't been able to recreate it yet. I'll see what I can do.

KevinH · 11-07-2017, 01:36 PM

I have pm'd and asked that they pm you the link to the problem ePub. I should have kept it a bit longer until we were sure we understood what is going on

DiapDealer · 11-07-2017, 01:45 PM

Thanks. We'll get it eventually.

theducks · 11-07-2017, 08:29 PM

Quote:

Originally Posted by JustinThought

Wow! I don't want to say that that was quick....but that was quick!

I can change my "workflow" so that I don't set the semantics before creating the TOC, instead doing it afterward. I might add, this issue has only come up with this author, because he has the Table Of Contents From Hell.

Thank you a bunch!

Using Sigil to Generate a HTML TOC sets all flags needed

My understanding:You need to clear the tag if you regenerate (and delete the old one, since now, it will not over write)

JustinThought · 11-07-2017, 11:45 PM

I ran through the process with another book, and I made sure to remove the semantics labeling the open window as the Table of Contents, and when I generated the HTML one, it went through without any problems. So I think that works as a temporary avoidance method. Of course, Ctrl-S is super-simple to hit. I'm kind of OCD about saving every time I've made more changes than I want to lose.

Thanks, DiapDealer and KevinH!

JustinThought · 11-09-2017, 11:24 AM

Quote:

Originally Posted by DiapDealer

Thanks. We'll get it eventually.

I'm assuming you've gotten it by now. I'm curious, have you been able to reproduce the problem? --And more specifically, I'm wondering if there's anything I've placed into the file that is causing the issue.

The reason I ask is, I have another file from the same series that I've been able to crash 100% of the times I've tried it. (And NOT crash 100% of the times I've removed the semantics before generating the TOC.)

But it seems to be specific to making a copy of the original TOC page before generating the new TOC. When I don't do that, I don't get the crash.

Just wonderin' if I can be of more assistance.

DiapDealer · 11-09-2017, 11:41 AM

Yes. Sorry. I meant that we'd eventually "get" the bug nailed down.

And yes, I've gotten Sigil to crash with both your test epub and others, but it's not been a 100% consistent thing for me. When performing the exact same steps, I'm experiencing different outcomes. Sometimes your epub (and all epubs) crash at the point of html toc generation, and sometimes your epub (and the same epubs that crashed before) don't crash at all.

I've not tried Kevin's latest change yet, but if it eliminates the problem altogether, I'll stop worrying about tracking down the exact nature of the bug at some point.

exaltedwombat · 11-10-2017, 09:51 AM

If you want to use ta customised layout for the HTML TOC, might it be a better idea to NOT use the automatic Create HTML TOC function but just add links manually to a normal HTML file, formatted to your specification?

DiapDealer · 11-15-2017, 06:11 PM

Since building/using a version of Sigil with Kevin's commit to address this issue, I've not been able to get Sigil to crash using the steps provided (with the test epub or any other) at all.

Therefore ... I'm officially going to stop worrying about why it was only sporadically crashing on me when using the old code.

KevinH · 11-15-2017, 06:17 PM

Good to know. Thanks for testing it.

Stevex · 11-28-2017, 06:08 PM

Will there be a new release of Sigial at some point, for those of us who dont want to have to compile it to get the fixes?

DiapDealer · 11-28-2017, 06:18 PM

Oh, yes. There will be a new release at some point. I can't speak for Kevin, but things have just been too hectic for me to prepare my parts of a new release (at least one that I can be assured doesn't introduce any new issues). The holidays looming, aren't helping any.

Stevex · 11-29-2017, 06:17 AM

Quote:

Originally Posted by DiapDealer

Oh, yes. There will be a new release at some point. I can't speak for Kevin, but things have just been too hectic for me to prepare my parts of a new release (at least one that I can be assured doesn't introduce any new issues). The holidays looming, aren't helping any.

Ok Thank you. Understand about time pressure... Hopefully January then ;-)

Cheers and thanks a lot

11-07-2017, 12:51 PM	#16
DiapDealer Grand Sorcerer Posts: 27,547 Karma: 193191846 Join Date: Jan 2010 Device: Nexus 7, Kindle Fire HD	I can't get it to crash on my Windows machine either. Is there something other than making sure the html toc (which is listed in the guide as the toc) is open in Code View before generating the html toc? Do I need a specific test case epub? My Windows machine is using Qt5.6.2 (same Qt the official Sigil release uses) and my Linux machine is using Qt5.9.2. Last edited by DiapDealer; 11-07-2017 at 12:58 PM.

11-07-2017, 01:27 PM	#17
KevinH Sigil Developer Posts: 7,637 Karma: 5433388 Join Date: Nov 2009 Device: many	I deleted the test case but perhaps the op will pm you with it as he did me. All I had to do was open that ePub, and then open the current html toc in Codeview. By default I have the pane for the toc ncx open on the left and preview pane open on the right. I only tested by removing the guide entry (all worked) and by manually closing HTML toc (again all worked). If I didn't do either and tried to create HTML toc, the crash happened 100% of the time Last edited by KevinH; 11-07-2017 at 01:29 PM.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Articles repeated in different feed sections	scissors	Recipes	8	10-19-2012 11:27 AM
Repeated contents in The Economist	Steven630	Recipes	5	06-21-2012 09:35 PM
PRS-350 Repeated syncing	Jeanw	Sony Reader	9	04-09-2012 04:28 PM
First Article Repeated for Friday Fax	rjgrigaitis	Recipes	2	02-21-2012 02:55 PM
Repeated crash after computer connection	roguefan99	Kobo Reader	2	07-23-2010 11:36 PM

11-07-2017, 01:32 PM	#18
DiapDealer Grand Sorcerer Posts: 27,547 Karma: 193191846 Join Date: Jan 2010 Device: Nexus 7, Kindle Fire HD	There must be something about that specific toc or epub, then. Because I haven't been able to recreate it yet. I'll see what I can do.

11-07-2017, 01:36 PM	#19
KevinH Sigil Developer Posts: 7,637 Karma: 5433388 Join Date: Nov 2009 Device: many	I have pm'd and asked that they pm you the link to the problem ePub. I should have kept it a bit longer until we were sure we understood what is going on

11-07-2017, 01:45 PM	#20
DiapDealer Grand Sorcerer Posts: 27,547 Karma: 193191846 Join Date: Jan 2010 Device: Nexus 7, Kindle Fire HD	Thanks. We'll get it eventually.

11-07-2017, 11:45 PM	#22
JustinThought Groupie Posts: 171 Karma: 3517858 Join Date: May 2016 Location: Monterrey, Mexico Device: Samsung Tab-3 7"	I ran through the process with another book, and I made sure to remove the semantics labeling the open window as the Table of Contents, and when I generated the HTML one, it went through without any problems. So I think that works as a temporary avoidance method. Of course, Ctrl-S is super-simple to hit. I'm kind of OCD about saving every time I've made more changes than I want to lose. Thanks, DiapDealer and KevinH!

11-09-2017, 11:41 AM	#24
DiapDealer Grand Sorcerer Posts: 27,547 Karma: 193191846 Join Date: Jan 2010 Device: Nexus 7, Kindle Fire HD	Yes. Sorry. I meant that we'd eventually "get" the bug nailed down. And yes, I've gotten Sigil to crash with both your test epub and others, but it's not been a 100% consistent thing for me. When performing the exact same steps, I'm experiencing different outcomes. Sometimes your epub (and all epubs) crash at the point of html toc generation, and sometimes your epub (and the same epubs that crashed before) don't crash at all. I've not tried Kevin's latest change yet, but if it eliminates the problem altogether, I'll stop worrying about tracking down the exact nature of the bug at some point.

11-10-2017, 09:51 AM	#25
exaltedwombat Guru Posts: 878 Karma: 2457540 Join Date: Nov 2011 Device: none	If you want to use ta customised layout for the HTML TOC, might it be a better idea to NOT use the automatic Create HTML TOC function but just add links manually to a normal HTML file, formatted to your specification?

11-15-2017, 06:11 PM	#26
DiapDealer Grand Sorcerer Posts: 27,547 Karma: 193191846 Join Date: Jan 2010 Device: Nexus 7, Kindle Fire HD	Since building/using a version of Sigil with Kevin's commit to address this issue, I've not been able to get Sigil to crash using the steps provided (with the test epub or any other) at all. Therefore ... I'm officially going to stop worrying about why it was only sporadically crashing on me when using the old code.

11-15-2017, 06:17 PM	#27
KevinH Sigil Developer Posts: 7,637 Karma: 5433388 Join Date: Nov 2009 Device: many	Good to know. Thanks for testing it.

11-28-2017, 06:08 PM	#28
Stevex Addict Posts: 225 Karma: 15318 Join Date: Nov 2015 Device: Kobo Glo HD	Will there be a new release of Sigial at some point, for those of us who dont want to have to compile it to get the fixes?

11-28-2017, 06:18 PM	#29
DiapDealer Grand Sorcerer Posts: 27,547 Karma: 193191846 Join Date: Jan 2010 Device: Nexus 7, Kindle Fire HD	Oh, yes. There will be a new release at some point. I can't speak for Kevin, but things have just been too hectic for me to prepare my parts of a new release (at least one that I can be assured doesn't introduce any new issues). The holidays looming, aren't helping any.