12-18-2020, 03:22 AM | #1 |
Wizard
Posts: 1,023
Karma: 10963125
Join Date: Mar 2013
Location: Guben, Brandenburg, Germany
Device: Kobo Clara 2E, Tolino Shine 3
|
Strange error message
Windows 10, 64 bit, Sigil v. 1.4.3.
Recently, at opening Sigil, I sometimes receive this error message: Code:
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 (Der Vorgang wurde erfolgreich beendet.) Sigil version: 1.4.3 Runtime Qt: 5.12.9 Compiled Qt: 5.12.9 System: Windows 10 (10.0) Architecture: x86_64 |
12-18-2020, 08:57 AM | #2 |
Sigil Developer
Posts: 7,644
Karma: 5433388
Join Date: Nov 2009
Device: many
|
A google search of the error message produced this:
https://bugreports.qt.io/browse/QTBUG-52397 https://bugreports.qt.io/browse/QTBUG-58322 https://www.mobileread.com/forums/sh....php?p=3951007 So it appears to be OpenGL related and Qt Related. Did you have a large number of Sigil instances open at the same time? Have you tried updating your video driver or make video driver related changes? |
12-18-2020, 09:13 AM | #3 |
Sigil Developer
Posts: 7,644
Karma: 5433388
Join Date: Nov 2009
Device: many
|
Upon further investigation, it seems to be caused by an out of memory error when allocating memory for a shared memory space. Or by trying to allocate memory too late after initialization. I would double check my video driver then reboot my entire computer to make sure a memory leak in some application is not causing problems at the system level.
Not much of a Windows person so perhaps DiapDealer may have a better idea of what is going on here. |
12-18-2020, 09:36 AM | #4 |
Grand Sorcerer
Posts: 27,549
Karma: 193191846
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
|
I've had the error come up rarely on both Linux and Windows. And like the OP, it never seemed to cause any issues after dismissing it. I haven't encountered it in a long time (though my time spent using Sigil on Windows is rather limited these days).
|
12-18-2020, 11:34 AM | #5 |
Guru
Posts: 692
Karma: 2180740
Join Date: Jan 2017
Location: Poland
Device: Misc
|
I run into such a bug from time to time (Windows 10), but I have never caught it twice in a row. Usually, the next launch of Sigil starts the program without a problem.
I have an old computer and the "latest" drivers are 8 years old, so even if it's related to the graphics card or drivers, there's nothing I can do about it. I remember this change in the code, but I have the feeling that I see this message on average once every two months anyway. I do not report it because: - I usually work on my build, which may have other issues related to my changes, so I don't want to call the guards when only my private build is on fire, - I can't repeat it until many weeks have passed and the error message reappears. It is difficult to debug an error that does not want to be caught. |
12-18-2020, 11:42 AM | #6 | |
Sigil Developer
Posts: 7,644
Karma: 5433388
Join Date: Nov 2009
Device: many
|
That change:
QCoreApplication::setAttribute(Qt::AA_ShareOpenGLC ontexts); is interesting in that the backtraces attached to those Qt bug reports and others that google found showed that the specific error code 0 was associated with failures to allocate shared memory for openGL (which uses in 4 meg blocks). So it may be related to the problem? Kevin Quote:
|
|
12-18-2020, 11:50 AM | #7 |
Guru
Posts: 692
Karma: 2180740
Join Date: Jan 2017
Location: Poland
Device: Misc
|
If you mean that with too little memory available in the system (or too defragmented to allocate enough space) – it is possible. I put a lot of strain on my computer, so sometimes memory is too low.
|
12-18-2020, 06:39 PM | #8 |
Grand Sorcerer
Posts: 27,549
Karma: 193191846
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
|
I've played with Qt::AA_ShareOpenGLContexts in the past, but I'm fairly certain I've seen the error with and without it.
|
12-18-2020, 06:50 PM | #9 |
Sigil Developer
Posts: 7,644
Karma: 5433388
Join Date: Nov 2009
Device: many
|
Good to know.
|
12-18-2020, 06:54 PM | #10 |
Grand Sorcerer
Posts: 27,549
Karma: 193191846
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
|
That said: I'm not entirely sure it's necessary. I just know I've see some suggest that it's necessary for QtWebEngine.
Last edited by DiapDealer; 12-19-2020 at 12:02 PM. |
12-19-2020, 10:35 AM | #11 |
Wizard
Posts: 1,023
Karma: 10963125
Join Date: Mar 2013
Location: Guben, Brandenburg, Germany
Device: Kobo Clara 2E, Tolino Shine 3
|
|
12-19-2020, 10:38 AM | #12 | |
Wizard
Posts: 1,023
Karma: 10963125
Join Date: Mar 2013
Location: Guben, Brandenburg, Germany
Device: Kobo Clara 2E, Tolino Shine 3
|
Quote:
|
|
12-19-2020, 04:33 PM | #13 |
Grand Sorcerer
Posts: 27,549
Karma: 193191846
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
|
I've had it happen on brand-new hardware with the very latest drivers. I'm convinced it's a rare race condition of some kind that's causing a spurious warning, to be honest. That's on Windows, mind you.
|
12-19-2020, 07:25 PM | #14 |
Bibliophagist
Posts: 35,428
Karma: 145525534
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Forma, Clara HD, Lenovo M8 FHD, Paperwhite 4, Tolino epos
|
Just to toss in that I've seen that error message 3 or 4 times and it doesn't seem to cause any issues nor is it repeatable. I've seen it using the builtin display with the Intel video driver and external monitors using the Nvidia driver though a docking station.
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Error: Error communicating with device message | techie6 | Devices | 5 | 04-02-2018 09:25 PM |
KindleGen error message: E1003 Unknown error in class String. | Doitsu | Kindle Formats | 1 | 06-25-2014 12:29 PM |
Help! I see a strange error message when I connect my ECO Reader to my PC | vixta | Introduce Yourself | 3 | 04-20-2011 09:42 AM |
error message: ERROR ITMS-4099: "Invalid ISBN: [#] at Book (MZItmspBookPac | NewDay | ePub | 3 | 10-07-2010 01:47 PM |
Strange Error Message - Anybody Else | Hughdal | Sony Reader | 4 | 05-27-2009 06:04 PM |