@
Kevin - Oh yes it matters
My tests were done within a single instance of Sigil, I started it from start->search->sigil, then
File->Open junk1.epub, scribbled in it, saved it,
File->Open junk2.epub, scribbled in it - if Bookview and Preview were active it crashed when I did the scribble, otherwise not.
In this scenario there is one process - i.e. only one main window
If I double click on epubs in file manager I get a process (window) for each EPUB - no crashing in that scenario.
It was this that prompted me to stick my oar in, as its not my standard way of working
Quote:
Originally Posted by ebookreadr
The crash happens when I open a new book while having the previous book still open in Sigil.
|
I start most programs from the data - particularly viewers, editors etc.
BR
Quote:
Originally Posted by KevinH
Hi BetterRed
Again I did not know that. On Mac OS X, double-clicking in the Finder (equivalent of Explorer) will generally open a new Window in the current app (all with a single process).
Can you recreate this Windows Crashing at all? Does it matter (crashingwise) if you use File->Open on Sigil versus launching another process? Which one crashes? Or is it both? It is really hard to believe that in this day and age, that one process can cause a second process to crash if not at a driver level or kernel level (ring 0)? So I am assuming the bug report was only for using File->Open in Sigil.
Thanks,
KevinH
|