Quote:
Originally Posted by Doitsu
Any epub that will produce the error that you reported.
(Note that you can't post commercial books on MR.)
|
I'm afraid it's not so simple. After reading your reply, I was just looking for a file that displayed the error when 'usage' was set to 'true' and I ran through about 8 files that were all good and correctly displayed a number of 'less than ideal' features (not to call them epub errors).
Then the next file produced that error message in my post above. I thought there must be some significant difference between this file and the previous eight. I went back to those previous eight files and they too then produced the error message.
Now every file I try produces that error message when 'usage: true' is set.
That confirms what I thought about yesterday's and this morning's performance: that I had successfully used the plugin with 'usage: true'. It appears that for a while, all works correctly, and then after several files (or after a certain interval?) nothing works correctly.
The 'fault' lies elsewhere than in the epub files. I have tried removing the plugin and reinstalling from the download zip in the first post to this thread. I removed the json preferences file which caused the new installation of the plugin to go check and download an update (as it did yesterday, too). The results were the same: nothing worked with 'usage: true'.
I shut down Sigil for about an hour and then came back and read your reply so went looking for a 'bad' file and the results are in my first para above.
So.... I'm using UbuntuStudio 18.04 (waiting for 20.04.1 to come out any day soon). Is it a consequence of my OS? Is some 'garbage' building up somewhere after repetitive use of the plugin? Remember how Windows95 used to run out of memory after opening and closing a couple of applications - and then failed with the BSOD?
I have checked that when I close Sigil, the process is killed and when I open another file, Sigil starts with a new process.