Sigil-0.9.12 Released

[KevinH]

My guess is your performance problems are similar to RbnJrg's. Please try booting into safe mode to confirm. Your problem like RbnJrg's may be unrelated to ini corruption and so following BetterRed's instructions will be important for all future versions of Sigil as well.

[icallaci]

Originally Posted by KevinH

My guess is your performance problems are similar to RbnJrg's. Please try booting into safe mode to confirm. Your problem like RbnJrg's may be unrelated to ini corruption and so following BetterRed's instructions will be important for all future versions of Sigil as well.

I'll give it a try when I get a chance. It may be a couple of days before I can report back.

[Mister L]

I finally had a bit of time and did a clean re-install of 12 today and *so far* it seems to be working smoothly (however it hasn't been running very long, either, so I suppose that's not conclusive), but i see in the interval there have been further developpements and the recommendation now is to revert to 10 and wait for a new version.

I will do that then (I would have had to anyway in the immediate as I need my clips and saved searches).

Thanks to the team and to everyone who has helped troubleshoot this issue. I look forward to trying out the updated version of Sigil when a stable release is available.

[Mister L]

Originally Posted by Mister L

I finally had a bit of time and did a clean re-install of 12 today and *so far* it seems to be working smoothly (however it hasn't been running very long, either, so I suppose that's not conclusive), but i see in the interval there have been further developpements and the recommendation now is to revert to 10 and wait for a new version.

I will do that then (I would have had to anyway in the immediate as I need my clips and saved searches).

Thanks to the team and to everyone who has helped troubleshoot this issue. I look forward to trying out the updated version of Sigil when a stable release is available.

Spoke too soon. Immediately after writing this I closed Sigil so that I could revert to 10 and... it crashed, as it was doing last week. If they can be of any help (it hadn't been running long at all and they are still the default prefs with no personalisation yet), here are the ini files from the new clean install of 12 which just crashed as well as 2 weird-looking (temp?) files which were in there too.

[DiapDealer]

Originally Posted by Mister L

Spoke too soon. Immediately after writing this I closed Sigil so that I could revert to 10 and... it crashed, as it was doing last week. If they can be of any help (it hadn't been running long at all and they are still the default prefs with no personalisation yet), here are the ini files from the new clean install of 12 which just crashed as well as 2 weird-looking (temp?) files which were in there too.

Wait ... this is the first I've heard of an honest-to-goodness "crash" of Sigil 0.9.12 on Windows. Did I miss a report?

[Mister L]

Originally Posted by DiapDealer

Wait ... this is the first I've heard of an honest-to-goodness "crash" of Sigil 0.9.12 on Windows. Did I miss a report?

Hm, not sure if that's the right description. Last week I was having a lot of trouble with it freezing / being unresponsive, in particular every single time I would try to close a window it would freeze ("not responding"). Today I closed the window and got the Windows crash message. Sorry I wasn't paying close enough attention when it happened, I don't think I got quite the same message as last week but I did have to dismiss the message to tell Windows to stop "looking for a solution". Also last week it would freeze and I would have to kill the process in the task manager, today it quit "unexpectedly" (I mean, it wasn't that unexpected since I was trying to close the window anyway, but apparently it was not a clean normal shut down).

[KevinH]

The sigil.ini.lock file shows the crash happened when trying to update the settings file. The wierd looking temp file is part of Settings too.

Before starting up Sigil again, please delete the sigili.ini.lock file and the crazy temp file. Your other ini files do not appear to be corrupted in any way.

[Mister L]

Originally Posted by KevinH

The sigil.ini.lock file shows the crash happened when trying to update the settings file. The wierd looking temp file is part of Settings too.

Before starting up Sigil again, please delete the sigili.ini.lock file and the crazy temp file. Your other ini files do not appear to be corrupted in any way.

Hm, that's weird, because like I said it was fine (and I didn't even try to update the settings because I was hoping to find a way to import my settings from 10) until it crashed when I closed it after it had been idle a while (long enough for me to write the message above). But it was literally when I clicked the X button that it crashed.

I've already reverted back to 10 with another clean install; I need my clips / searches too much to use 12 regularly until I can import them, and as I'd read that a new (hopefully stable) version is coming soon I preferred to follow the recommendation to wait for that one.

[theducks]

Originally Posted by DiapDealer

Wait ... this is the first I've heard of an honest-to-goodness "crash" of Sigil 0.9.12 on Windows. Did I miss a report?

I had 12 do a spontaneous abort. 1 time.
I can't even remember exactly what I was doing (TOC or a rename), which is why I said nothing. W10 x64

I have reverted to 10 upon your general advivice

[BetterRed]

Sometimes when a program is in a 'Not Responding' state you can press the red X, that's when you'll sometimes get the "Trying to find a solution blah blah " msg, but other times you have to kill the Task.

FWIW - I did a little test here with Safe Mode minimal

• Two of my startup 3rd party Windows Tasks were running, Malwarebytes and CheetahSync, and some of my 3rd party Context Menu tasks.
• The significance of that is: just because a program misbehaves in Safe mode doesn't mean the cause is not a 3rd party 'gadget'
• But it does narrow down the candidates to those Safe mode did not exclude.

That's why i prefer my CCleaner approach, I can exclude the things Windows forgot (that's almost a line from an ad - can't remember for what )

BR

[icallaci]

I ran Sigil in Safe Mode (no networking) and the performance/memory problems remained. Unfortunately, I forgot to save the .ini files before I closed Sigil (some habits are hard to break), but I had been checking them periodically as I worked and did not notice any corruption.

[BetterRed]

@icallaci - could you try my 'disable everything with CCleaner suggestion', if the performance issues remain then that would take the 3rd party program interference option off the table - or at least push it the bleedin' edge

As I wrote in my post above yours, when I started Windows in Safe Mode minimal - some 3rd party startup programs, including shell extensions, were not excluded.

BR

[icallaci]

OK, so I installed CCleaner and disabled everything, then rebooted in Safe Mode and spent about two hours fiddling with an epub by opening files, closing files, opening images, closing images, searching, running various plugins, etc. Memory usage climbed steadily, with Sigil slowing down and becoming nonresponsive for periods of up to 30 seconds. I did remember to zip up the .ini files this time. Lo and behold, I had two extra sigil.ini files (but they had garbage extensions instead of .ini). Zip file is attached below.

Originally Posted by BetterRed

@icallaci - could you try my 'disable everything with CCleaner suggestion', if the performance issues remain then that would take the 3rd party program interference option off the table - or at least push it the bleedin' edge

As I wrote in my post above yours, when I started Windows in Safe Mode minimal - some 3rd party startup programs, including shell extensions, were not excluded.

BR

[KevinH]

Looked at the ini files and there are two ini temp files dated over an hour apart. The actual ini file, searches.ini, and index.ini showed no corruption.

This is so very strange. We are planning to release a Sigil 0.9.13 hopefully this weekend that reverts the ini codec back to what it was in Sigil-0.9.10.

Once it has been released we can use it to rule out ini related reasons for what you are seeing.

Thanks!

[BetterRed]

@KevinH - given how few users are suffering I'm wondering if it could be something to do with image processing (illaci wrote "... opening images, closing images,...") - my assumption being that most users wouldn't doing much with images.

@illaci - can you confirm you disabled all the Context Menu items in CCleaner, sorry to be a pain in the you know..., but I'm sure you understand...

BR