![](https://secure.gravatar.com/avatar/c7cac86fed6ebc81bd83add827b77267.jpg?s=120&d=mm&r=g)
Hi Gary,
I cannot reproduce your issue using v1.1 on multiple different Win10 machines. Am I understanding you correctly that to reproduce it I only have to
1. open Inkscape and leave it open 2. open e.g. an image editor like Gimp or mspaint, open any random raster image I have lying around
to make Inkscape crash?
That is so basic, if that was a widespread issue, we would have heard of it. Nevertheless, the best cause of action is that you create an issue here https://inkscape.org/report to get your issue on our radar.
René
Am 23.09.2021 um 01:03 schrieb gjr gjr@rockley.net:
Since V1.0
When opening ANY Non exported, Non embedded, Non Related image file with ANY other "GRAPHICS/RASTER" app causes inkscape to crash with a GDI BUS error if INSKSCAPE (NOT RESPONDING) is active in memory.
Getting sick of it. For crying out loud - even attaching image to email crashes inkscape.
I'm running Win 8.1 (yes, I know).
I have tried assigning admin perms to Inkscape and gdibus.exe, to no avail.
Here's what I think,
you are lockcing the gdi bus memory, ASSUMING THAT ANY CALL TO THE GDI IS FOR YOU, THEN YOU RECEIVE A NULL RESPONSE AND YOU HAVE ZERO ERROR HANDLING.
Not every gdi bus call is for inkscape.
Fix this.
Seriously, I have lost so much stuff because of this - it corrupts text areas and gradients and I am getting sick of it.
For crying out loud, handling a null response is coding 101!
Kind Regards,
Gary
--
..................... Gary Rockley Tel +1 512 519 9593 Cel +1 651-216-4726 _______________________________________________ Inkscape Devel mailing list -- inkscape-devel@lists.inkscape.org To unsubscribe send an email to inkscape-devel-leave@lists.inkscape.org