Insckape fails to start on windows 10 - possible preferences file issue

[Tristan Chaplin]

I have install Inkscape 0.92.2 (tried 32bit and 64bit separately) on Windows 10, the installation works but when I start Inkscape, the processes starts but then exits after a few seconds, with no message. When I run it from the command line, there is no message either.

I noticed that when I uninstall it, it asks if I want to remove my preference file at
"C:\Users chaplin\AppData\Roaming..."

There is a large space after "Users", and my username starts with a t, is it possible that the directory C:\Users\tchaplin\ is interpreted as a having a tab in it? I notice that there is no Inkscape directory in that location, so it was never made. Could this be causing the problem? If so what can I do about it?

[Patrick Storz (ede123)]

The tab issue seams real but I suspect it's only a cosmetic issue (at least we never had any similar reports and I doubt there aren't any other users whose name starts with a "t").

As a first test could you try launching "inkscape.com" from a command line instead of inkscape.exe (provided that you did not already did that)?
Due to limitations of Windows the .exe won't ever generate any output on the Windows console (that's why we ship the .com wrapper).

[Tristan Chaplin (tristan-chaplin)]

Thanks for the suggestion, but I get the same lack-of-message when running inkscape.com. Is there any other way to get an output or log?

[Tristan Chaplin (tristan-chaplin)]

If I try inkview.com on a svg, I get a GUI message this time from Windows just sating "A problem caused the program to stop working correctly. Please close the program." No more detail.

[Patrick Storz (ede123)]

OK, thanks for feedback.

Just to be sure:
Did you verify you installed Inkscape into an empty directory? If you install into a location were Inkscape was previously installed and the uninstall failed for whatever reason this could cause problems.

Some steps that might help us to debug this issue:
- execute "set" in cmd.exe and attach output here
  It prints all environment variables so we can check if there
  is anything suspicious that could cause problems.
- execute in cmd.exe
  "set PATH=C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem"
  then run Inkscape.com again and see if it still crashes
  (this rules out conflicts with other libraries on search path)

If all of that does not give us any hints we'd have to actually debug the application using a debugger...

[Tristan Chaplin (tristan-chaplin)]

Apologies for the delayed reply. Changing PATH did not help.

Here is the output from set (before changing PATH)

ALLUSERSPROFILE=C:\ProgramData
APPDATA=C:\Users\tchaplin\AppData\Roaming
CommonProgramFiles=C:\Program Files\Common Files
CommonProgramFiles(x86)=C:\Program Files (x86)\Common Files
CommonProgramW6432=C:\Program Files\Common Files
COMPUTERNAME=MU00043142
ComSpec=C:\WINDOWS\system32\cmd.exe
FPS_BROWSER_APP_PROFILE_STRING=Internet Explorer
FPS_BROWSER_USER_PROFILE_STRING=Default
HOMEDRIVE=C:
HOMEPATH=\Users\tchaplin
LOCALAPPDATA=C:\Users\tchaplin\AppData\Local
LOGONSERVER=\\IDM-ADDS02-V02
NUMBER_OF_PROCESSORS=8
OneDrive=C:\Users\tchaplin\OneDrive
OS=Windows_NT
Path=C:\ProgramData\Oracle\Java\javapath;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Google\Google Apps Sync\;C:\Program Files (x86)\Lithnet\Lithnet.MpUpdate;C:\Program Files\MATLAB\R2017a\runtime\win64;C:\Program Files\MATLAB\R2017a\bin;C:\Program Files\TortoiseSVN\bin;C:\Users\tchaplin\AppData\Local\Microsoft\WindowsApps;
PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC
PROCESSOR_ARCHITECTURE=AMD64
PROCESSOR_IDENTIFIER=Intel64 Family 6 Model 60 Stepping 3, GenuineIntel
PROCESSOR_LEVEL=6
PROCESSOR_REVISION=3c03
ProgramData=C:\ProgramData
ProgramFiles=C:\Program Files
ProgramFiles(x86)=C:\Program Files (x86)
ProgramW6432=C:\Program Files
PROMPT=$P$G
PSModulePath=C:\Program Files\WindowsPowerShell\Modules;C:\WINDOWS\system32\WindowsPowerShell\v1.0\Modules
PUBLIC=C:\Users\Public
SESSIONNAME=Console
SystemDrive=C:
SystemRoot=C:\WINDOWS
TEMP=C:\Users\tchaplin\AppData\Local\Temp
TMP=C:\Users\tchaplin\AppData\Local\Temp
UATDATA=C:\WINDOWS\CCM\UATData\D9F8C395-CAB8-491d-B8AC-179A1FE1BE77
USERDNSDOMAIN=AD.MONASH.EDU
USERDOMAIN=MONASH
USERDOMAIN_ROAMINGPROFILE=MONASH
USERNAME=tchaplin
USERPROFILE=C:\Users\tchaplin
windir=C:\WINDOWS

I'm in a large organisation, perhaps some anti-virus in the SOE is interfering, I'll investigate that.

[Patrick Storz (ede123)]

There does not seem to be anything suspicious in the environment variables.

Next thing to try is actually running a debugger. You can find a compatible version of gdb at [1] or [2] (for 32/64-bit respectively). To debug:
- Copy mingw*/bin/gdb.exe
  to your inkscape installation directory
- on a console execute "gdb inkscape.exe"
- then enter the command "run" and hit enter
- when Inkscape crashes enter "bt" in the console window,
  hit enter and paste the whole output here

[1] http://repo.msys2.org/mingw/i686/mingw-w64-i686-gdb-8.0-2-any.pkg.tar.xz
[2] http://repo.msys2.org/mingw/x86_64/mingw-w64-x86_64-gdb-8.0-2-any.pkg.tar.xz

[Tristan Chaplin (tristan-chaplin)]

Thanks for the fast reply.

This the output, it shows many thousands of error messages that look pretty much the same, bellow are the first few. Is that a problem with gdp though?

(gdb) run
Starting program: C:\Program Files\Inkscape\inkscape.exe
[New Thread 13048.0x1a0]
[New Thread 13048.0xec]
[New Thread 13048.0x2de8]
[New Thread 13048.0x2794]
[New Thread 13048.0xfbc]
[New Thread 13048.0x1e28]
[New Thread 13048.0x209c]
[New Thread 13048.0x2e30]
[New Thread 13048.0x2720]
[New Thread 13048.0x214c]
[New Thread 13048.0x654]

Thread 1 received signal SIGSEGV, Segmentation fault.
Python Exception <type 'exceptions.NameError'> Installation error: gdb.execute_unwinders function is missing:
0x00007ffde9d779df in ntdll!RtlAllocateHeap () from C:\WINDOWS\SYSTEM32\ntdll.dll
(gdb) bt
Python Exception <type 'exceptions.NameError'> Installation error: gdb.execute_unwinders function is missing:
Python Exception <type 'exceptions.ImportError'> No module named gdb.frames:
#0 0x00007ffde9d779df in ntdll!RtlAllocateHeap () from C:\WINDOWS\SYSTEM32\ntdll.dll
#1 0x00007ffde9dd4000 in ntdll!EtwEventProviderEnabled () from C:\WINDOWS\SYSTEM32\ntdll.dll
Python Exception <type 'exceptions.NameError'> Installation error: gdb.execute_unwinders function is missing:
#2 0x00007ffde9dfdaee in ntdll!memset () from C:\WINDOWS\SYSTEM32\ntdll.dll
Python Exception <type 'exceptions.NameError'> Installation error: gdb.execute_unwinders function is missing:
#3 0x00007ffde9d780b7 in ntdll!RtlAllocateHeap () from C:\WINDOWS\SYSTEM32\ntdll.dll
Python Exception <type 'exceptions.NameError'> Installation error: gdb.execute_unwinders function is missing:
#4 0x00007ffde9d763aa in ntdll!RtlReAllocateHeap () from C:\WINDOWS\SYSTEM32\ntdll.dll
Python Exception <type 'exceptions.NameError'> Installation error: gdb.execute_unwinders function is missing:
#5 0x00007ffde9d75a5f in ntdll!RtlReAllocateHeap () from C:\WINDOWS\SYSTEM32\ntdll.dll
Python Exception <type 'exceptions.NameError'> Installation error: gdb.execute_unwinders function is missing:
#6 0x00007ffde9d75961 in ntdll!RtlReAllocateHeap () from C:\WINDOWS\SYSTEM32\ntdll.dll
Python Exception <type 'exceptions.NameError'> Installation error: gdb.execute_unwinders function is missing:
#7 0x00007ffde9e3bc2f in ntdll!RtlpNtMakeTemporaryKey () from C:\WINDOWS\SYSTEM32\ntdll.dll
Python Exception <type 'exceptions.NameError'> Installation error: gdb.execute_unwinders function is missing:
#8 0x00007ffde9dfd06c in ntdll!memset () from C:\WINDOWS\SYSTEM32\ntdll.dll
Python Exception <type 'exceptions.NameError'> Installation error: gdb.execute_unwinders function is missing:
#9 0x00007ffde9d75a5f in ntdll!RtlReAllocateHeap () from C:\WINDOWS\SYSTEM32\ntdll.dll
Python Exception <type 'exceptions.NameError'> Installation error: gdb.execute_unwinders function is missing:
#10 0x00007ffde9d75961 in ntdll!RtlReAllocateHeap () from C:\WINDOWS\SYSTEM32\ntdll.dll
Python Exception <type 'exceptions.NameError'> Installation error: gdb.execute_unwinders function is missing:
#11 0x00007ffde9919f17 in realloc () from C:\WINDOWS\System32\msvcrt.dll
Python Exception <type 'exceptions.NameError'> Installation error: gdb.execute_unwinders function is m...

[Tristan Chaplin (tristan-chaplin)]

Forgot to mention this was for the 64 bit version, with the 64bit gdb, e.g.

C:\Program Files\Inkscape>gdb inkscape.exe
Python Exception <type 'exceptions.ImportError'> No module named gdb:
C:\Program Files\Inkscape\gdb.exe: warning:
Could not load the Python gdb module from `c:\mingw64\share\gdb/python'.
Limited Python support is available from the _gdb module.
Suggest passing --data-directory=/path/to/gdb/data-directory.

GNU gdb (GDB) 8.0
Copyright (C) 2017 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-w64-mingw32".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from inkscape.exe...(no debugging symbols found)...done.

[Tristan Chaplin (tristan-chaplin)]

Sorry I just looked the message more closely, it looks like the mingw64 directory should be copied to c:.

I did that and now get this:

C:\Program Files\Inkscape>gdb inkscape.exe
GNU gdb (GDB) 8.0
Copyright (C) 2017 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-w64-mingw32".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from inkscape.exe...(no debugging symbols found)...done.
(gdb) run
Starting program: C:\Program Files\Inkscape\inkscape.exe
[New Thread 1172.0x33f4]
[New Thread 1172.0x19a0]
[New Thread 1172.0x2378]
[New Thread 1172.0x2034]
[New Thread 1172.0x2dd0]
[New Thread 1172.0x2e2c]
[New Thread 1172.0x2ed8]
[New Thread 1172.0x3b4]
[New Thread 1172.0x1130]
[New Thread 1172.0x32dc]
[New Thread 1172.0x1b84]

Thread 1 received signal SIGSEGV, Segmentation fault.
0x00007ffde9d779df in ntdll!RtlAllocateHeap () from C:\WINDOWS\SYSTEM32\ntdll.dll
(gdb) bt
#0 0x00007ffde9d779df in ntdll!RtlAllocateHeap () from C:\WINDOWS\SYSTEM32\ntdll.dll
#1 0x00007ffde9dd4000 in ntdll!EtwEventProviderEnabled () from C:\WINDOWS\SYSTEM32\ntdll.dll
#2 0x00007ffde9dfdaee in ntdll!memset () from C:\WINDOWS\SYSTEM32\ntdll.dll
#3 0x00007ffde9d780b7 in ntdll!RtlAllocateHeap () from C:\WINDOWS\SYSTEM32\ntdll.dll
#4 0x00007ffde9d763aa in ntdll!RtlReAllocateHeap () from C:\WINDOWS\SYSTEM32\ntdll.dll
#5 0x00007ffde9d75a5f in ntdll!RtlReAllocateHeap () from C:\WINDOWS\SYSTEM32\ntdll.dll
#6 0x00007ffde9d75961 in ntdll!RtlReAllocateHeap () from C:\WINDOWS\SYSTEM32\ntdll.dll
#7 0x00007ffde9e3bc2f in ntdll!RtlpNtMakeTemporaryKey () from C:\WINDOWS\SYSTEM32\ntdll.dll
#8 0x00007ffde9dfd06c in ntdll!memset () from C:\WINDOWS\SYSTEM32\ntdll.dll
#9 0x00007ffde9d75a5f in ntdll!RtlReAllocateHeap () from C:\WINDOWS\SYSTEM32\ntdll.dll
#10 0x00007ffde9d75961 in ntdll!RtlReAllocateHeap () from C:\WINDOWS\SYSTEM32\ntdll.dll
#11 0x00007ffde9919f17 in realloc () from C:\WINDOWS\System32\msvcrt.dll
#12 0x00000000685f72b6 in ?? () from C:\Program Files\Inkscape\libglib-2.0-0.dll
#13 0x00000000685c38a6 in ?? () from C:\Program Files\Inkscape\libglib-2.0-0.dll
#14 0x00000000685c3d3f in ?? () from C:\Program Files\Inkscape\libglib-2.0-0.dll
#15 0x000000006c3849c1 in ?? () from C:\Program Files\Inkscape\libgdk-win32-2.0-0.dll
#16 0x0000000063a67c62 in ?? () from C:\Program Files\Inkscape\libgobject-2.0-0.dll
#17 0x0000000063a4aaaf in ?? () from C:\Program Files\Inkscape\libgobject-2.0-0.dll
#18 0x0000000063a4c360 in ?? () from C:\Program Files\Inkscape\libgobject-2.0-0.dll
#19 0x0000000063a4c932 in ?? () from C:\Program Files\Inkscape\libgobject-2.0-0.dll
#20 0x000000006c38538f in ?? () from C:\Program Files\Inksc...

[Patrick Storz (ede123)]

Could you attach the full backtrace ("Type <return> to continue")?

Unfortunately everything that happens in the part you've shown is in third-party libraries and Windows DLLs themselves... Let's hope the rest of the backtrace gives some pointers as to where the issue could be located.

[Tristan Chaplin (tristan-chaplin)]

Oh ok, here it is, starting at about 1500 because the cmd screen was full:

#1579 0x0000000063a4c360 in ?? () from C:\Program Files\Inkscape\libgobject-2.0-0.dll
#1580 0x0000000063a4c932 in ?? () from C:\Program Files\Inkscape\libgobject-2.0-0.dll
#1581 0x000000006c38538f in ?? () from C:\Program Files\Inkscape\libgdk-win32-2.0-0.dll
#1582 0x000000006c34c9a9 in ?? () from C:\Program Files\Inkscape\libgdk-win32-2.0-0.dll
#1583 0x000000006c38446b in ?? () from C:\Program Files\Inkscape\libgdk-win32-2.0-0.dll
#1584 0x0000000063a67c62 in ?? () from C:\Program Files\Inkscape\libgobject-2.0-0.dll
#1585 0x0000000063a4aaaf in ?? () from C:\Program Files\Inkscape\libgobject-2.0-0.dll
#1586 0x0000000063a4c360 in ?? () from C:\Program Files\Inkscape\libgobject-2.0-0.dll
#1587 0x0000000063a4c932 in ?? () from C:\Program Files\Inkscape\libgobject-2.0-0.dll
#1588 0x000000006c38538f in ?? () from C:\Program Files\Inkscape\libgdk-win32-2.0-0.dll
#1589 0x000000006c34c9a9 in ?? () from C:\Program Files\Inkscape\libgdk-win32-2.0-0.dll
#1590 0x000000006c38446b in ?? () from C:\Program Files\Inkscape\libgdk-win32-2.0-0.dll
#1591 0x0000000063a67c62 in ?? () from C:\Program Files\Inkscape\libgobject-2.0-0.dll
#1592 0x0000000063a4aaaf in ?? () from C:\Program Files\Inkscape\libgobject-2.0-0.dll
#1593 0x0000000063a4c360 in ?? () from C:\Program Files\Inkscape\libgobject-2.0-0.dll
#1594 0x0000000063a4c932 in ?? () from C:\Program Files\Inkscape\libgobject-2.0-0.dll
#1595 0x000000006c38538f in ?? () from C:\Program Files\Inkscape\libgdk-win32-2.0-0.dll
#1596 0x000000006c34c9a9 in ?? () from C:\Program Files\Inkscape\libgdk-win32-2.0-0.dll
#1597 0x000000006c38446b in ?? () from C:\Program Files\Inkscape\libgdk-win32-2.0-0.dll
#1598 0x0000000063a67c62 in ?? () from C:\Program Files\Inkscape\libgobject-2.0-0.dll
---Type <return> to continue, or q <return> to quit---
#1599 0x0000000063a4aaaf in ?? () from C:\Program Files\Inkscape\libgobject-2.0-0.dll
#1600 0x0000000063a4c360 in ?? () from C:\Program Files\Inkscape\libgobject-2.0-0.dll
#1601 0x0000000063a4c932 in ?? () from C:\Program Files\Inkscape\libgobject-2.0-0.dll
#1602 0x000000006c38538f in ?? () from C:\Program Files\Inkscape\libgdk-win32-2.0-0.dll
#1603 0x000000006c34c9a9 in ?? () from C:\Program Files\Inkscape\libgdk-win32-2.0-0.dll
#1604 0x000000006c38446b in ?? () from C:\Program Files\Inkscape\libgdk-win32-2.0-0.dll
#1605 0x0000000063a67c62 in ?? () from C:\Program Files\Inkscape\libgobject-2.0-0.dll
#1606 0x0000000063a4aaaf in ?? () from C:\Program Files\Inkscape\libgobject-2.0-0.dll
#1607 0x0000000063a4c360 in ?? () from C:\Program Files\Inkscape\libgobject-2.0-0.dll
#1608 0x0000000063a4c932 in ?? () from C:\Program Files\Inkscape\libgobject-2.0-0.dll
#1609 0x000000006c38538f in ?? () from C:\Program Files\Inkscape\libgdk-win32-2.0-0.dll
#1610 0x000000006c34c9a9 in ?? () from C:\Program Files\Inkscape\libgdk-win32-2.0-0.dll
#1611 0x000000006c38446b in ?? () from C:\Program Files\Inkscape\libgdk-win32-2.0-0.dll
#1612 0x0000000063a67c62 in ?? () from C:\Program Files\Inkscape\libgobject-2.0-0.dll
#1613 0x0000000063a4aaaf in ?? () from C:\Program Files\Inkscape\libgobject-2.0-0.dll
#1614 0x0000000063a4c360 in ?...

[Patrick Storz (ede123)]

Oh, wow, that looks certainly wrong...

Inkscape code is not mentioned on a single line and it seems we're either caught in and endless loop of some kind (potentially causing RtlAllocateHeap to fail eventually as apparent from the output you posted before) or in some GDK windowing loop.

I'm afraid I'm a bit clueless as to what make of this right now... I'm afraid this might be a very fundamental issue with GDK.
Do you have by any idea what could distinguish your system from others with respect to graphics / graphics drivers / display / connected monitors / etc.?

[Patrick Storz (ede123)]

P.S. You can also try to redirect gdb output to a file using

gdb > output.txt

(you'll have to execute "run"/"bt" commands "blind" in that case)

[Tristan Chaplin (tristan-chaplin)]

The system has a NVIDIA Quadro K600. I just reinstalled the latest drivers ("385.69-quadro") but that didn't seem to help (attached is the output). Other than that it's a pretty standard single display via DVI to a HP L2245wg monitor.

[Patrick Storz (ede123)]

To rule out a gtk issue you you could try to run the gtk demo:
- download [1]
- copy "gtk-demo.exe" from the /bin directory
  to the Inkscape installation directory
- copy the share/ folder to the Inkscape installation directory
- execute "gtk-demo.exe" from cmd.exe

(you can play around a bit with it and have an eye on the command line output - maybe something suspicious comes up)

[1] http://repo.msys2.org/mingw/x86_64/mingw-w64-x86_64-gtk2-2.24.31-4-any.pkg.tar.xz

[Tristan Chaplin (tristan-chaplin)]

Perhaps it is a GTK problem:

C:\Program Files\Inkscape>gtk-demo.exe

I get the GUI message: gtk-demo.exe has stopped working.

Attached is the gdb output, it looks very similar to the Inkscape error.

There are quite a few mentions of 32 in there, this is supposed to be a 64bit install, is that ok?

[Patrick Storz (ede123)]

Hi Tristan, yes, if even the gtk-demo crashes it is certainly not an Inkscape issue.

It might still be a packaging problem but I'd say that's unlikely as it seems to be an isolated issue. If you want to make 100% sure you can install MSYS2 - which is the currently recommended method to obtain GTK on Windows [1] and is also what Inkscape uses since 0.92.2 - and test there again. (in "Step 2" you should install mingw-w64-x86_64-gtk2 though as Inkscape 0.92.x still uses gtk2; of course you can cross check with gtk3; skip all other steps, they're unnecessary).

Going forward I can only recommend you to carry this upstream [2] (see section "Bug Reporting" to the right). Maybe gtk folks are able to help you out and/or know a few tricks to make gtk explain why it's failing...

> There are quite a few mentions of 32 in there,
> this is supposed to be a 64bit install, is that ok?

If you mean "libgdk-win32" that's perfectly fine. "win32" is a short (and slightly imprecise) name for the "Windows API" [3] which all applications compiled for Windows use. libgdk-win32 is simply the Windows backend library of GDK [4].

[1] https://www.gtk.org/download/windows.php
[2] https://www.gtk.org/development.php
[3] https://en.wikipedia.org/wiki/Windows_API
[4] https://en.wikipedia.org/wiki/GDK

[Tristan Chaplin (tristan-chaplin)]

Hi Eduard,

Thanks, looks like I will need to take it to GTK.

Although I didn't quite understand what I should do after installing gtk in MSY, I did:

pacman -S mingw-w64-x86_64-gtk2

Then is the idea to run Inkscape? Or is there supposed to be a new gtk-demo.exe somewhere?

Cheers,
Tristan

[Patrick Storz (ede123)]

After installing mingw-w64-x86_64-gtk2 you can run the gtk-demo again:
- Open a MinGW shell (simply use the "MSYS2 MinGW 64-bit" shortcut)
- execute "gtk-demo" (it will be on your search path)

If it still crashes, then it's definitely an issue with gtk2...

[Tristan Chaplin (tristan-chaplin)]

Ah yep, that crashes too.

Thanks for all your help, I'll take it to gtk.

[Tristan Chaplin (tristan-chaplin)]

Hi Eduard,

Just to let you know, I submitted this over at GTK (https://bugzilla.gnome.org/show_bug.cgi?id=789635) but it's not looking promising. Since I have quite a limited use case for inkscape, I'm just using it in a virtual linux machine now, so I guess you can close this issue off. It's probably due to something weird about this workstation I'm using.

Thanks for all your help though, it was much appreciated.

Cheers,
Tristan

[Patrick Storz (ede123)]

Thanks! Let's see and hope...

One thing you could still try which does not require much effort (at least if you have your MSYS2 installation still around) is crosscheck with gtk3 as I suggested in comment #17.

Basically you'd do (on an MSYS2 MinGW shell):
- pacman -S mingw-w64-x86_64-gtk3
  to install gtk3
- gtk3-demo
  to run the gtk3 equivalent of the demo.

If the issue reproduces in gtk3, too, maybe chances might slightly increase that someone will look into it.

[Qantas94Heavy (qantas94heavy)]

As OP is no longer using Inkscape on Windows, further updates are unlikely, so this bug will be closed.

If you have a similar problem with the latest Inkscape version, please use our new bug tracker: https://inkscape.org/report. Thank you!

[Qantas94Heavy (qantas94heavy)]

This can't be reproduced with Inkscape 0.92.4 on Windows 10, so it will be closed.

Closed by: https://gitlab.com/Qantas94Heavy