Sigil-1.2.0 Released

[DiapDealer]

Originally Posted by Monaghan

Running Windows. Is there any way I can send you a log in this case? I should note this is a full-updated, regularly restarted workstation.

Steps to consistently reproduce the crash would probably prove more useful on Windows. But the Windows Event Viewer should at least provide a bit of info related to the crash in question.

[Notjohn]

Originally Posted by BetterRed

As you can imagine I'm sitting here, confined to barracks, having a quiet chuckle.

I know it wasn't you guys, and that it's too late now, but IMO not using F2 for file rename is like not using ctrl+c, ctrl+v for coffee and pasta. Needless to say that's what I have changed it to

BR

The first key letter to vanish from my Logitech K350 keyboard was the P, and the C was weakening. That was after ten months. Logitech was kind enough to send me a replacement.

[Monaghan]

Originally Posted by DiapDealer

Steps to consistently reproduce the crash would probably prove more useful on Windows. But the Windows Event Viewer should at least provide a bit of info related to the crash in question.

Here we go:

Copy/pasting a div between xhtml files.

Faulting application name: Sigil.exe, version: 1.2.0.0, time stamp: 0x5e7f50cb
Faulting module name: Qt5Widgets.dll, version: 5.12.7.0, time stamp: 0x5e777b61
Exception code: 0xc0000005
Fault offset: 0x0000000000054790
Faulting process ID: 0x1e3c
Faulting application start time: 0x01d60f1492b849f3
Faulting application path: C:\Program Files\Sigil\Sigil.exe
Faulting module path: C:\Program Files\Sigil\Qt5Widgets.dll
Report ID: 0907c2e2-83d8-4964-a2f9-e5cb724dccc1
Faulting package full name: 
Faulting package-relative application ID:

[KevinH]

Just in case, how exactly did you copy and paste? Using a mouse or the shortcut keys or the menus? Are the crashes random? Or if you repeat the same steps, how many times does it take for the crash to happen? How long has Sigil been open? Have you tried setting your own temp path in Sigil settings to see if that will help?

[DiapDealer]

Do you happen to have any utilities installed for manipulating the clipboard? Badly constructed shell extensions are also notorious for causing crashes in Qt apps on Windows. Have you installed any new utilities around the time you upgraded to Sigil 1.2?

[Monaghan]

Originally Posted by KevinH

Just in case, how exactly did you copy and paste? Using a mouse or the shortcut keys or the menus? Are the crashes random? Or if you repeat the same steps, how many times does it take for the crash to happen? How long has Sigil been open? Have you tried setting your own temp path in Sigil settings to see if that will help?

• Ctrl-C 🡒 Ctrl-V

• Crashes seemingly random, however only happens when copy-pasting or when search and replace is used.

• ~5 crashes per hour.

• Sigil hard crashes, and next crash can be only a couple of minutes later.

Originally Posted by DiapDealer

Do you happen to have any utilities installed for manipulating the clipboard? Badly constructed shell extensions are also notorious for causing crashes in Qt apps on Windows. Have you installed any new utilities around the time you upgraded to Sigil 1.2?

• No clipboard utilities installed.

Thanks for the assistance, both.

[KevinH]

What about a utility or program to manage keyboard shortcuts?
Given the large number of Windows users, and how often you say it is crashing, we would be getting lots of bug reports but no one else seems to be seeing these crashes.

Have you tried renaming your sigil.ini file just in case it got corrupted somehow?

[BetterRed]

Suggestion: If not already done, and other suggestions exhausted

• Use Task Manager to disable everything in Startup, restart Windows, and try Sigil again.
• If that doesn't help, use CCleaner (or similar)->Tools->Start Up and disable everything 'foreign' in Scheduled Tasks, restart Windows, and try Sigil again.
• If that doesn't help, use CCleaner (or similar)->Tools->Start Upo and disable everything 'foreign' in Context Menu, restart Windows, and try Sigil again.
• If that doesn't help, I'm out :-)

By 'foreign' I mean everything that's not Microsoft or device related (e.g NVDIA, Logitech etc essentials). I do it in three steps to narrow the search, and I prefer this way over Safe mode a) because it gives me more control and b) I'm never sure what Safe Mode eliminates,

BR

[Monaghan]

Originally Posted by KevinH

What about a utility or program to manage keyboard shortcuts?
Given the large number of Windows users, and how often you say it is crashing, we would be getting lots of bug reports but no one else seems to be seeing these crashes.

Have you tried renaming your sigil.ini file just in case it got corrupted somehow?

Thanks for this. I don't use any utilities for keyboard shortcuts. Will rename the sigil.ini when I have time to go back and try the latest version again—I reverted to an older release for my work in the meantime. For info, I've had no crashes in four days (~3 hours per day) with this previous version.

Originally Posted by BetterRed

Suggestion: If not already done, and other suggestions exhausted

• Use Task Manager to disable everything in Startup, restart Windows, and try Sigil again.
• If that doesn't help, use CCleaner (or similar)->Tools->Start Up and disable everything 'foreign' in Scheduled Tasks, restart Windows, and try Sigil again.
• If that doesn't help, use CCleaner (or similar)->Tools->Start Upo and disable everything 'foreign' in Context Menu, restart Windows, and try Sigil again.
• If that doesn't help, I'm out :-)

By 'foreign' I mean everything that's not Microsoft or device related (e.g NVDIA, Logitech etc essentials). I do it in three steps to narrow the search, and I prefer this way over Safe mode a) because it gives me more control and b) I'm never sure what Safe Mode eliminates,
BR

Thanks for all. Will report back once work calms down and I have time to try the latest release again.

[DiapDealer]

What is the older version of Sigil you're using that seems to be crash-free?

[hesprus]

I just installed version 1.2.0 on my Windows 10 notebook, and it won't even start completely - it crashes almost immediately, forcing me to use task manager to shut it down. I had this problem a couple months ago, as well and uninstalled software. Interesting to note that Calibre's e-book preview function does exactly the same thing, in that it just freezes up. I shut off Windows Defender, and I looked at settings on the graphics card, but nothing jumps out as a potential block. Running on MSI, Intel i7-8750H, 2.20GHz, 32 g RAM, Windows 10 Pro 1909 OS build: 18363.752

[KevinH]

Try renaming your sigil.ini file to something else and then starting up Sigil. Crashes on startup are typically due to ini file corruption.

[DNSB]

I am seeing a fairly consistent error using Sigil. This seems to happen the first time when I am opening a non-Sigil standard epub from within a calibre library with a space in the library name using the Open with plugin

Sigil has encountered a problem.

Sigil may need to close.

Error info: Critical: ARB::createContext: wglCreateContextAttribsARB() failed (GL error code: 0x0) for format: QSurfaceFormat(version 2.0, options QFlags<QSurfaceFormat::FormatOption>(), depthBufferSize 24, redBufferSize -1, greenBufferSize -1, blueBufferSize -1, alphaBufferSize -1, stencilBufferSize 8, samples 0, swapBehavior QSurfaceFormat::DefaultSwapBehavior, swapInterval 1, colorSpace QSurfaceFormat::DefaultColorSpace, profile  QSurfaceFormat::NoProfile), shared context: 0x30000 (The operation completed successfully.)
Sigil version: 1.2.0
Runtime Qt: 5.12.7
Compiled Qt: 5.12.7
System: Windows 10 (10.0)
Architecture: x86_64

[KevinH]

Are you using Sigils "open with" or Calibre's "open with"? If the latter, I would suspect a clash of Qt environment variables or versions since Calibre uses Qt 5.14 or even later while Sigil uses Qt 5.12.7.

Do any of these failures happen without the use of "open with", ie.completely separating the two programs environments?

[DiapDealer]

I meant to ask the others if they're launching Sigil via calibre. That always seems to bite us in the ass when it comes to trying to debug issues.

If the issue goes away when launching Sigil normally, then that gives us a good place to start.

We need people to understand that opening Sigil via either of calibre's Open With options is not a "normal" Sigil launch. We'll do all we can to make sure Sigil works with calibre's inherent Open With feature, but support for the Open With Plugin has been on-again/off-again forever. I'm tired of chasing it quite frankly.