Inkscape has a fundamental crack in its code. It does not dump properly. It is as though the CPU were getting clogged with "blood clots." This gets worse as one uses the software because - first - heat builds up and modifies the way the CPU works. Second - the number of calculations the system is doing is increasing with each new command. Trying to do anything with it just makes it worse.
I have been experiencing this near daily for 20 years. The problem comes out of software design philosophies that existed in the 1980's. Inkscape, which started at that time, is still burdened by those philosophies. They are not the only software to encounter them. Blender used to have the same issue. They switched to GPU dominance. Inkscape has apparently pulled multi threading and GPU resource allocation from post 1.0 iterations. ???
The best thing I have been able to do is completely shut the system down and let it cool. I actually bought a gamer's laptop system to get better heat performance. It worked, but it still has issues. Also, if you are working hard on a project and are making a lot of changes - do a manual save every hour or so. By save, I mean completely close the file and reopen it.
If you are developing an icon, you probably won't have any issues with the clogging. However, if you are developing anything larger than a few hundred kilobytes - it grinds.
The recent crashes I have had were more related to other Windows activities that touched the display or filesystem. I don't use Inkscape on Linux daily, but have it for reference.
Would reliance on the GPU provide a level of insulation from the complicators?
If the management know memory load has been a fundamental problem for so long - why are they not fixing it? It can be fixed. It has been fixed by others. Why not inkscape?
I do not and never have had any issues with the developers.
How can we encourage more of them to work on the project?
Why can't they refactor the code others have created under the "free and open software" ideology? Its there to use. Why are we seeing a dark theme instead of a resolution for such a basic issue?
Why are developers saying they won't help the project? Misdirected focus?
Not an expert at all this .. but when a program crashes 5 to 6 times within 15 minutes, to me, there is a serious problem. I have used all kinds of open source programs and this is the ONLY one That crashes this many times
In my experience the replies to our concerns come in three varieties.
1. Those poor coders - they work so hard - give em a break will ya?
2. This is free software. The 10 minutes you spend an hour dealing with work arounds and fails DO NOT add up. They do not result in dozens or hundreds of hours of lost time per year at XYZ conversion rate. Time IS NOT money. Your 20 hours of wasted time per year DO NOT equate to $200 at a $10 per hour rate. They DO NOT equate to $1000 at another rate. INKSCAPE IS FREE !
3. If you don't like what we do - go away.
Sad.
Being a database of graphic elements - this software has A LOT to offer. Archeologists, lawyers, doctors, gamers and everyone who needs to see information in scale changes could use this project.
@cajunmashphoto, Inkscape has been very stable for 99% of its users through the .92.x versions. Not perfect, but very stable. It's a reasonable option for many users.
Version 1.1 has great new features, but many Glowforge users have been using the .92.xx versions for years.
@ NELCHAI, You should go away. Ad hominem denigration of the developers is self-serving, infantile and pathetic. If you can't contribute constructively, please go. You have other options in software and other outlets to express your opinions. If you continue to bash on the developers, you will be banned.
I am not bashing the developers. I think they want to solve problems like these but are being tasked with the creation of a dark theme and such instead. I don't think its the devs.
When bugs are identified, the development response is prioritised by: how serious is the problem? how frequently does it occur? how easily can it be fixed?
As participating users, the most important thing we can do is report bugs and crashes as we encounter them. Issues that are well-documented will receive more attention so the effort we spend researching our bugs will be rewarded with quicker solutions.
This forum is a place where users like you and me volunteer our time to help other users. Very few of us write code (not me anyway) but we want to contribute in some way to the project. I understand your frustration, but this is not the place to rage against the system.
If a memory problem has been frequently reported and known of for years [ decades now? ] why has it not been fixed?
It is not the developers who want to fix it that are to blame.
It is probably the management who has not prioritized it.
Also, before you start throwing a tantrum and start threatening to ban this and that - please show me where the code of conduct prohibits valid criticism and questions like - why has it not been fixed?
And - my comment about how the question would be responded to - is exactly how it was responded to.
Sad. Being a database of graphic elements - this software has A LOT to offer. Archeologists, lawyers, doctors, gamers and everyone who needs to see information in scale changes could use this project. bad, narcissistic, amateurish, management
These comments and those just above are neither friendly nor helpful.
This topic is locked and the user @NELCHAI is hereby notified that continued unhelpful comments will result in being banned.
Forum Testing Petty complaints
Inkscape.org
Inkscape has a fundamental crack in its code. It does not dump properly. It is as though the CPU were getting clogged with "blood clots." This gets worse as one uses the software because - first - heat builds up and modifies the way the CPU works. Second - the number of calculations the system is doing is increasing with each new command. Trying to do anything with it just makes it worse.
I have been experiencing this near daily for 20 years. The problem comes out of software design philosophies that existed in the 1980's. Inkscape, which started at that time, is still burdened by those philosophies. They are not the only software to encounter them. Blender used to have the same issue. They switched to GPU dominance. Inkscape has apparently pulled multi threading and GPU resource allocation from post 1.0 iterations. ???
The best thing I have been able to do is completely shut the system down and let it cool. I actually bought a gamer's laptop system to get better heat performance. It worked, but it still has issues. Also, if you are working hard on a project and are making a lot of changes - do a manual save every hour or so. By save, I mean completely close the file and reopen it.
If you are developing an icon, you probably won't have any issues with the clogging. However, if you are developing anything larger than a few hundred kilobytes - it grinds.
Memory load has been an issue for ages.
The recent crashes I have had were more related to other Windows activities that touched the display or filesystem. I don't use Inkscape on Linux daily, but have it for reference.
Would reliance on the GPU provide a level of insulation from the complicators?
If the management know memory load has been a fundamental problem for so long - why are they not fixing it? It can be fixed. It has been fixed by others. Why not inkscape?
It is a very small group of devs. Good, dedicated people, just not a lot of them, compared to other projects.
I do not and never have had any issues with the developers.
How can we encourage more of them to work on the project?
Why can't they refactor the code others have created under the "free and open software" ideology? Its there to use. Why are we seeing a dark theme instead of a resolution for such a basic issue?
Why are developers saying they won't help the project? Misdirected focus?
Not an expert at all this .. but when a program crashes 5 to 6 times within 15 minutes, to me, there is a serious problem. I have used all kinds of open source programs and this is the ONLY one That crashes this many times
YES
In my experience the replies to our concerns come in three varieties.
1. Those poor coders - they work so hard - give em a break will ya?
2. This is free software. The 10 minutes you spend an hour dealing with work arounds and fails DO NOT add up. They do not result in dozens or hundreds of hours of lost time per year at XYZ conversion rate. Time IS NOT money. Your 20 hours of wasted time per year DO NOT equate to $200 at a $10 per hour rate. They DO NOT equate to $1000 at another rate. INKSCAPE IS FREE !
3. If you don't like what we do - go away.
Sad.
Being a database of graphic elements - this software has A LOT to offer. Archeologists, lawyers, doctors, gamers and everyone who needs to see information in scale changes could use this project.
bad, narcissistic, amateurish, management
@cajunmashphoto, Inkscape has been very stable for 99% of its users through the .92.x versions. Not perfect, but very stable. It's a reasonable option for many users.
Version 1.1 has great new features, but many Glowforge users have been using the .92.xx versions for years.
@ NELCHAI, You should go away. Ad hominem denigration of the developers is self-serving, infantile and pathetic. If you can't contribute constructively, please go. You have other options in software and other outlets to express your opinions. If you continue to bash on the developers, you will be banned.
1, 2, and 3 all in one!
I am not bashing the developers. I think they want to solve problems like these but are being tasked with the creation of a dark theme and such instead. I don't think its the devs.
my wife suggest I may have made someone cry
I'm sorry
can we get along?
I'm not a programmer, but....
When bugs are identified, the development response is prioritised by:
how serious is the problem?
how frequently does it occur?
how easily can it be fixed?
These two links are illuminating. The first tells users how to report bugs to developers and the second tells developers how to triage the bug reports submitted by users.
https://inkscape.org/contribute/report-bugs/
https://gitlab.com/inkscape/inbox/-/blob/master/Guidelines.md
As participating users, the most important thing we can do is report bugs and crashes as we encounter them. Issues that are well-documented will receive more attention so the effort we spend researching our bugs will be rewarded with quicker solutions.
This forum is a place where users like you and me volunteer our time to help other users. Very few of us write code (not me anyway) but we want to contribute in some way to the project. I understand your frustration, but this is not the place to rage against the system.
If a memory problem has been frequently reported and known of for years [ decades now? ] why has it not been fixed?
It is not the developers who want to fix it that are to blame.
It is probably the management who has not prioritized it.
Also, before you start throwing a tantrum and start threatening to ban this and that - please show me where the code of conduct prohibits valid criticism and questions like - why has it not been fixed?
And - my comment about how the question would be responded to - is exactly how it was responded to.
Please, stop wasting my time. Fix the bug.
These comments and those just above are neither friendly nor helpful.
This topic is locked and the user @NELCHAI is hereby notified that continued unhelpful comments will result in being banned.