In the few hours since I started using Inkspace today I've had three crashes. No messages, just sudden closure.
I can't remember useful details of the first. The next was while trying to align two objects horizontally. The latest was while holding the Alt key down and pressing an arrow key, my first attempt to move a selected circle a tiny amount, as described here: https://www.google.co.uk/search?q=inkscape+move+object+single+pixel&ie=utf-8&oe=utf-8
Luckily one of the first things I did this morning was to read the stickies and promptly enable Autosave. But I made a fair bit of progress after the last (10 min) save, which I'll now have to repeat.
I'm now nervously saving manually ever few seconds! Is the program known to be unstable? Perhaps especially when used by novices? Is there a list of known bugs I can study so that I can avoid certain areas please?
--------------------
EDIT: Yet another crash. Just editing text... Should I install an earlier version? Is there consensus on the most stable?
If it matters, I'm running Win 10 version 20H2 (OS Build 19042.1415)
EDIT: …and more., latest was while using arrow key to move selected text. Yet that same text had been moved successfully before. So inconsistent.
Another puzzling aspect is that directly after the crash I followed what what is now becoming a familiar (tedious) procedure, namely opened both folders where my work is being saved:
1. My project folder where I was regularly saving the file Panel-02.svg, the last one time-stamped 18:16
2. The Autosave folder, where the last file was: C:\Users\terry\AppData\Local\Microsoft\Windows\INetCache\inkscape\automatic-save-0-2021_12_16_18_18_14-14504-1.svg, time-stamped 18:18 The previous one was 18:07, under 10 mins earlier.
But the odd things is that my project folder has an additional file, also time-stamped 18:18, called Panel-02.svg.2021_12_16_18_18_44.0.svg
Is this normal? It looks as if directly before crashing the program saves two files, in same 'autosave' format, one in each folder.
Is 1.1.1 regarded as less buggy? After much further reading I’m wondering if 1.0.2 would be preferable.
Before finishing for today I was up to about 10 crashes, and activity directly beforehand varied widely (and inconsistently). Also, no special characters in my text. And anyway as mentioned I’d moved it several times before with no problem.
I see many posts over the last year or so about Inkscape’s instability. Ten crashes in one day is bordering on unusable! So when I get this urgent project finished I’ll have to reconsider the options. I see that my Office 365 package includes Publisher, so although I really like Inkscape I may have to switch.
I’m still getting frequent crashes. It’s as if there is some sort of instability and/or memory issue with Inkscape, which is affected almost randomly by other activity on the PC.
I have also identified one activity that consistently causes the crash: fast repetition of the arrow key while moving an object.
I finished the urgent project, but intend to try other versions methodically when I get more time.
Meanwhile it would be good to hear from the developers.
On Mac I installed 1.2dev a day ago and it crashes on opening, on new from template till it refuses to open at all - until I restart the Mac. Now it´s working properly so far.
I see hier so many "reasons" why Inscape can crash, but it doesnt help. The question is, why the programm is so instable? I mean, I guess next time when I open window in my homeoffice, I can expect that it will crash, too. The reason will be - opened window.... Kind of funny, but it is actually not. There are lots of programms, that are not crashing under the same circumstances.
In the few hours since I started using Inkspace today I've had three crashes. No messages, just sudden closure.
I can't remember useful details of the first. The next was while trying to align two objects horizontally. The latest was while holding the Alt key down and pressing an arrow key, my first attempt to move a selected circle a tiny amount, as described here:
https://www.google.co.uk/search?q=inkscape+move+object+single+pixel&ie=utf-8&oe=utf-8
Luckily one of the first things I did this morning was to read the stickies and promptly enable Autosave. But I made a fair bit of progress after the last (10 min) save, which I'll now have to repeat.
I'm now nervously saving manually ever few seconds! Is the program known to be unstable? Perhaps especially when used by novices? Is there a list of known bugs I can study so that I can avoid certain areas please?
--------------------
EDIT: Yet another crash. Just editing text... Should I install an earlier version? Is there consensus on the most stable?
If it matters, I'm running Win 10 version 20H2 (OS Build 19042.1415)
EDIT: …and more., latest was while using arrow key to move selected text. Yet that same text had been moved successfully before. So inconsistent.
Another puzzling aspect is that directly after the crash I followed what what is now becoming a familiar (tedious) procedure, namely opened both folders where my work is being saved:
1. My project folder where I was regularly saving the file Panel-02.svg, the last one time-stamped 18:16
2. The Autosave folder, where the last file was:
C:\Users\terry\AppData\Local\Microsoft\Windows\INetCache\inkscape\automatic-save-0-2021_12_16_18_18_14-14504-1.svg, time-stamped 18:18
The previous one was 18:07, under 10 mins earlier.
But the odd things is that my project folder has an additional file, also time-stamped 18:18, called
Panel-02.svg.2021_12_16_18_18_44.0.svg
Is this normal? It looks as if directly before crashing the program saves two files, in same 'autosave' format, one in each folder.
Inkscape 1.1 (c68e22c387, 2021-05-23)
I would uninstall version 1.1 and try version 1.1.1. Then, let us know how it goes.
Text can be touchy if it has special characters.
Is 1.1.1 regarded as less buggy? After much further reading I’m wondering if 1.0.2 would be preferable.
Before finishing for today I was up to about 10 crashes, and activity directly beforehand varied widely (and inconsistently). Also, no special characters in my text. And anyway as mentioned I’d moved it several times before with no problem.
I see many posts over the last year or so about Inkscape’s instability. Ten crashes in one day is bordering on unusable! So when I get this urgent project finished I’ll have to reconsider the options. I see that my Office 365 package includes Publisher, so although I really like Inkscape I may have to switch.
I have the same problem since yesterday... It crashed for 30 Times for sure. Reason? I dont know. Version 1.1.1.
@Anastasiia_91, if it wasn't crashing before yesterday, there is likely a change in your system. Inkscape does not auto-update.
I’m still getting frequent crashes. It’s as if there is some sort of instability and/or memory issue with Inkscape, which is affected almost randomly by other activity on the PC.
I have also identified one activity that consistently causes the crash: fast repetition of the arrow key while moving an object.
I finished the urgent project, but intend to try other versions methodically when I get more time.
Meanwhile it would be good to hear from the developers.
On Mac I installed 1.2dev a day ago and it crashes on opening, on new from template till it refuses to open at all - until I restart the Mac. Now it´s working properly so far.
I see hier so many "reasons" why Inscape can crash, but it doesnt help. The question is, why the programm is so instable? I mean, I guess next time when I open window in my homeoffice, I can expect that it will crash, too. The reason will be - opened window.... Kind of funny, but it is actually not. There are lots of programms, that are not crashing under the same circumstances.
jimhilbert1 @jimhilbert1 , Inkscape is not an online app. AWS issues are not remotely related.
Anastasiia_91, Inkscape runs without crashing on most systems... tens of thousands of systems. Linux, Windows and Mac.
If you would like help resolving Inkscape issues on your system, follow the guidance on this page: https://inkscape.org/forums/questions/get-good-answers-here/.
Maybe related to this: https://gitlab.com/inkscape/inkscape/-/issues/2944. A workaround is mentioned. YMMV