I was working on an epub in Sigil. It's a novel and I was breaking it into chapters with the Split At Cursor button. Specifically I would do the first chapter in Book, then hit the Find feature (where I had "chapter" input). That would kick the Book into Code and I would then use the Find again to get to the next chapter.
Then I would use the Split at Cursor button to split off another chapter.
It worked perfectly for ten chapters, then suddenly bogged. It still worked but everything took like 30-45 seconds.
I shut Sigil down. I re-started the computer.
When the computer came back up and I brought up Sigil and opened the file it was even worse. First of all it took 45 seconds to open the file. Then whatever I did (no matter how slight) bogged it. I started watching the Task Manager and yeah it was Sigil tying up 100% of the CPU.
This window came up:
Quote:
|
The application Keyboard Input Methods has closed unexpectedly.
|
I'm on Xubuntu 15.04 Vivid.
I copied the "details" and attached them.
I re-launched the Keyboard Input Methods. (I thought that might somehow be the problem because earlier I was using the F5 key for the 'next spelling error' check.)
When I tried the file again in Sigil though it was the same result--totally bogged.
I made a copy and tried it in Sigil--same thing.
Anyway, then I started thinking the file is corrupt.
I opened a different epub in Sigil and it worked perfectly.
IF it is a corrupt file I only lost a day's work so it's no big deal. BUT I wonder if I did something to corrupt the file (it started as an odt, I turned it into an html in LibreOffice and input the html into Sigil). Maybe by switching back and forth between Book and Code via the Find search. AND I'm wondering if yesterday's file (I checked and it worked fine) is going to suffer the same fate (corruption--again if it is corruption).
And is there anything I can do to somehow deal with this thing more effectively than just keeping my fingers crossed and starting over?
Sorry for the novel (it's just less than the novel I was working on!). Thanks.