Not replicated in Inkscape 1.0.1 (3bc2e813f5, 2020-09-07) x32 bit and x64 bit Windows 10 or Arch (1.0.1-2). There is a long hang on preview and on load, but no crash
I do crash in 0.48.2 32 bit Windows 10 though (popup comes up but its all black and disappears before it renders properly). running from inkscape.com, I do see the following message though:
RegistryTOol: Could not create the registry key 'SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\inkscape.exe'
terminate called after throwing an instance of 'std::bad_alloc'
what(): std::bad_alloc
Emergency save activiated!
... (sorry, I'm typing out the error message, skipping this common bit)
***MEMORY-ERROR***: inkscape.exe[4036]: GSlice: failed to allocate 4088 bytes (alignment: 4096): Not enough space
------------
Since I no longer replicate in 1.0 on Windows 10, closing as fixed, as part of the bug migration to Gitlab (see https://alpha.inkscape.org/bug-migration/). If this problem does still occur for you in 0.92.5 or later, please create a new issue in our new bugtracker at inkscape.org/report (should redirect to it).
Not replicated in Inkscape 1.0.1 (3bc2e813f5, 2020-09-07) x32 bit and x64 bit Windows 10 or Arch (1.0.1-2). There is a long hang on preview and on load, but no crash
I do crash in 0.48.2 32 bit Windows 10 though (popup comes up but its all black and disappears before it renders properly). running from inkscape.com, I do see the following message though:
RegistryTOol: Could not create the registry key 'SOFTWARE\ Microsoft\ Windows\ CurrentVersion\ App Paths\inkscape.exe'
terminate called after throwing an instance of 'std::bad_alloc'
what(): std::bad_alloc
Emergency save activiated!
... (sorry, I'm typing out the error message, skipping this common bit)
***MEMORY-ERROR***: inkscape.exe[4036]: GSlice: failed to allocate 4088 bytes (alignment: 4096): Not enough space
------------
Since I no longer replicate in 1.0 on Windows 10, closing as fixed, as part of the bug migration to Gitlab (see https:/ /alpha. inkscape. org/bug- migration/). If this problem does still occur for you in 0.92.5 or later, please create a new issue in our new bugtracker at inkscape.org/report (should redirect to it).
Thanks for reporting this bug!