Hi,

Error messages in the Inkscape are not new to me and did not think much about them because
so far, there was an auto backup saved file.

But today during work Inkscape showed error messages and I could not find any backup file like earlier.
Therefore, I thought I should ask a question about those error messages.

Here is a text of the two error messages appeared in the following serial:

---------------------------
glibmm-ERROR **:
unhandled exception (type std::exception) in signal handler:
what: std::bad_alloc

aborting...
OK

--------------
Microsoft Visual C++ Runtime Library
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
OK

What I was doing when I got these messages?
I was using Pattern along path.
repeated stretched
snake
default settings(all zero)
duplicate checked
preview checked

The above error appeared seldom after clicking apply button.

Any advice will be appreciated.

Thank you

Ah, well I've recently learned that an "exception" can mean practically anything, in programming terms. It means the program asked something of the computer, and the computer didn't handle it properly. At least that's my non-technical understanding.

For some more meaningful info, I've seen that error in cases where I've apparently asked either Inkscape, or Inkscape and my computer system, to do too much. Sometimes if I work really fast, and I'm click, click, clicking away, it seems like the requests (clicks) get backed up and confused, and neither Inkscape or my computer can get them to work in the right order. I've also seen it when my file is 2 mb or larger (with 4 gb RAM). If you have less than 2 gb RAM, even 1 mb files can be too much. Filters (including blurs) can be especially troublesome sometimes.

It looks like you were working with the PAP LPE? Or were you using the PAP extension? I find the LPE's to be slightly buggy. They are still rather new to Inkscape, so that isn't surprising. I'm also not surprised when Inkscape crashes while I'm using an extension.

What I would question, is why the auto backup didn't work. Are you looking in the right place for the backup? I guess it would be in the place where you usually find them, unless you changed it in Inks Prefs. If there's a bug anywhere, it's in the auto backup, I would think. Because the auto backup is still fairly new.

Or maybe someone else can explain it better?

Hello Brynn,

Thank you for the detailed reply.
As I use computer for designing/animation/videos/photos editing for that purpose my computer is ok. Duo Core, Graphic card is fine, Memory, 4GB enough hard drive. All drivers are update.

I was not doing anything special as I am new, I do not know about tube or I do not know what is PAP or LPE. What I know is the pattern was not complicated even path was just a simple one. I used Pattern along path, nothing extra filters or else.

Regarding backup file, if I am not wrong one svg file is save in the Inkscape main folder or if I make sub-folder then inside working folder. However, the other non svg file is save on C:User/.... Also, XBEL files are save here.

But since this error message appeared there isn't any backup file that is why I was surprised.

Thank you

My understanding is that the bad_alloc exception is thrown when there's a problem allocating memory. In other words, Inkscape requested more memory to the OS and something went wrong with it. This doesn't necessarily mean that Inskcape ran out of memory, though, it could also be some buggy code or just "pure luck" which supposedly doesn't exist in computer world... but it happens.

Given the nature of the bug, maybe Inkscape just can't handle that and just crashes without any attempt to backup, after all, the data Inkscape was handling is corrupted for sure.

memory allocation on windows is more complicated than it should be....the application receives a particularly sized pool which it can fill as it sees fit. so the computer virtual + real memory could still have lots of room but the application can't use it. in fact you could have many gigabytes of physical (real) memory in windows but apps can't really use it all anyway. afaik there's no computer instruction on windows for "try to allocate" instead it's just "allocate", and if it's unsuccessful it's not easy for the app/windows to handle it well. in other words either the app or windows or both may crash or misbehave. for example try loading a several megabyte file into notepad or wordpad...you have to manually kill the app.
the low level details of things like pattern along path start using a lot of memory if there's quite a few nodes in the pattern. when doing these types of memory intensive things be sure to use wireframe mode and vacuum defs every once in a while. both improve performance and reduce chances for running out of memory.

the computer bug type allocation problem is when an application doesn't free up space within its' pool when objects are no longer needed, running out of memory much earlier than it should. the memory allocation and deallocation code is usually separate code on a feature by feature basis, thus some particular features of an application only cause this "memory leak".

chriswww wrote:memory allocation on windows is more complicated than it should be....the application receives a particularly sized pool which it can fill as it sees fit. so the computer virtual + real memory could still have lots of room but the application can't use it. in fact you could have many gigabytes of physical (real) memory in windows but apps can't really use it all anyway. afaik there's no computer instruction on windows for "try to allocate" instead it's just "allocate", and if it's unsuccessful it's not easy for the app/windows to handle it well. in other words either the app or windows or both may crash or misbehave. for example try loading a several megabyte file into notepad or wordpad...you have to manually kill the app.
the low level details of things like pattern along path start using a lot of memory if there's quite a few nodes in the pattern. when doing these types of memory intensive things be sure to use wireframe mode and vacuum defs every once in a while. both improve performance and reduce chances for running out of memory.

the computer bug type allocation problem is when an application doesn't free up space within its' pool when objects are no longer needed, running out of memory much earlier than it should. the memory allocation and deallocation code is usually separate code on a feature by feature basis, thus some particular features of an application only cause this "memory leak".

Hi,

Thank you for reply.
Would you mind talking more about that "wireframe mode and vacuum defs" what is that and how could I use?
Thanks

Uktrunie wrote:My understanding is that the bad_alloc exception is thrown when there's a problem allocating memory. In other words, Inkscape requested more memory to the OS and something went wrong with it. This doesn't necessarily mean that Inskcape ran out of memory, though, it could also be some buggy code or just "pure luck" which supposedly doesn't exist in computer world... but it happens.

Given the nature of the bug, maybe Inkscape just can't handle that and just crashes without any attempt to backup, after all, the data Inkscape was handling is corrupted for sure.

Hi,

Thank you for reply
----------------------------

That error could also occur if you have many other (or sometimes even one other) memory intesive programs running at the same time. For example, Photoshop and Inkscape. You know, if my security is running a scan, supposedly "in the background" I can have more Inkscape crashes than I have when they aren't running. It could have been something as simple as that. Maybe your computer was so bogged down, that Inkscape didn't have time to make the backup. If it's such a small file though, maybe having the backup isn't so important?

Vacuum Defs can help in large files, by removing unused data. File menu > Vacuum Defs. Does hurt anything to click, if you are unsure. The status bar will report how many things were removed. You can also help working in large files, by using View menu > Display mode > No Filters, or Outline. It causes filters not to be displayed (which I previously mentioned, can be problematic) in the case of No Filters Mode. Or in Outline mode, does not display filters or any fill or color info. But since you've said the file is not large, those will probably not help you.

PAP is Pattern Along Path. LPE is Live Path Effects. As I said, there are now 2 ways to use PAP -- there's an extension, and there's an LPE. I recall you had another topic, about having a problem with a tutorial, where the PAP extension was used in the tutorial. So I'm guessing you were using the extension. In general, your error message indicates some kind of memory problem. If you had the pattern and path selected in the wrong order, or....iir it's not the order of selection, but the z-order that's important. Anyway, if you have them mixed up, Inkscape could become bogged down trying to draw an impossible image, even if all there is on the canvas is the pattern and the path, and even if Inkscape were the only program you have running at the time.

Since you had it set to repeat and stretch the pattern, if you had the wrong one on top, then Inkscape was trying to use the path as the pattern and the pattern as the path. So it would make repeated copies of the path, along the paths in the pattern. Depending on the complexity of both pattern and path, that could cause some really wild and huge object!

If you still have the file, the SVG file, we could have a look at it. No guarantee that we could reproduce the error, but we could try. Also, I'll search Launchpad for bugs with the autosave feature.

Hi,

Thank you very much for detailed reply. I agree with you if another program is running in the background there is a chance program could crash. Same thing I tell in other forum and websites. Now a days we use computer but often do not know computer management. I always keep my data on external drives and keep drivers and software update so, processor can work smoothly.

Thank you for telling me what is PAP and LPE. I do not think I made a mistake in selecting pattern and path in wrong order BUT what I can remember and even later I faced a problem was, I clicked the LIVE PREVIEW in PAP and later when I wanted to un-check Inkscape had showed the same error message(may be I reacted quickly and at that time PAP was busy). Not only that last few days were strange and I have uninstalled the Inkscape.
Why? sometimes when, I moved simple object for few seconds I noticed as if the edge was bleeding . Which I can not stand and temporarily un-installed the Inkscape.

Therefore, I am sorry I am unable to attach SVG file or even a screen shot.

PS: now I know PAP but could not get Live Path Effects and extension.

Path menu > Live Path Effects is where all the LPEs can be found. And everything in Extensions menu is an extension.

Why? sometimes when, I moved simple object for few seconds I noticed as if the edge was bleeding .

I don't understand what you mean. But if it happens again, try and get a screenshot. Maybe we could recognize it by seeing it. Or do you mean that having Inkscape installed is making something happen on your computer, that you don't see happening when Inkscape is not installed? Well, in any case, if it happens again, try and get a screenshot

I wonder why my last reply in response to brynn is not here?

Anyway I have re-installed Inkscape and started using.
Since last two days everything is going fine.

It's probably nothing serious. I know for myself, from time to time, I''ll write a reply and forget to post it, lol. I'm not an expert, but I have the impression that every now and then the internet has a hiccup and eats a message

Anyway, I'm glad that everything seems to be working. Just remember to get a screenshot, if it happens again

Hi,

Thank you very much for taking time to clear it.
So far, Inkscape is working fine. I have made
two color palettes for inkscape.

I guess to talk and ask about color palette I should
start a new thread.

Thank you

Yes, please start a new thread for a new topic. But you might try searching first, to see if the question has already been asked and answered