Bad Allocation Errors

[l.hayesBQYR8]

While using the sculpting environment to create complex shapes, my fusion often crashes, with an error message saying 'Bad  Allocation'. 

Is there any way to prevent this? My system is fairly strong, running a GeForce 1050, a 2.5 GHz i5, and 8GB RAM, but i often experience very poor performance from fusion especially when editing a particular file (https://a360.co/2P0Wo3b). I have turned off all unnecessary effects and set my program to optimal performance.

While this is usually annoying, I make plenty of backups, and save every few minutes, so I never loose too much progress to crashes, but just today a 'bad allocation' error has actually prevented me from progressing at all.

When trying to transfer a certain body from the sculpting environment to the modelling environment, yet another 'bad allocation', but this time as a transferal error. 

This means I can't continue to work on this project, which is a major issue for me.

Screenshot included below

[mavigogun]

It would be great if you could attach files directly to your post in the future.    The linked to file didn't show a preview at the linked to page.    My instance of Fusion hung trying to load the file- I had to kill the process manually.

[mavigogun]

No better results on second attempt- hung my entire system for a while.    You might hand this file off to Development for examination.    What do you think, @jeff_strater?

[l.hayesBQYR8]

Yeah, the file is pretty hefty. The one body shown in the screenshot is very complex, but also has a lot of work put into it. Is there any way to simplify a super complex body in the sculpting environment which might work?

That body does seem to be the root of the problem, but 'Bad Allocation' messages show up with many of my files, so it's not exclusively this file which is a problem.

Is this a common thing, that fusion regularly crashes with semi-complex shapes, or is it just my system?

Also not entirely sure how to attach the file directly. My bad

[mavigogun]

The design finally loaded for me.    A few observations.    There are around 40 discrete Sculpt Bodies created in a single Timeline Feature.   The Body you have visible in the screencapture, 68, is self-intersecting, so can not be converted to a BREP- you'll have to find where Bodies pass through themselves and correct the geometry to something that could exist in the real world.     Performing Utilities > Repair Body on 68, there are around 24 5-Edged intersections flagged, and 4 problem intersections.    Follow Rule #1 and #2: create components    and name your stuff.    When you Finish Form this Sculpt Feature, Fusion will attempt to convert EVERY Sculpt Body, visible or not, to a BRep or Surface form.

You've built in a very high load on your system.   Many of the Sculpt Bodies- such as wheels, tyres -could occupy their own discrete Feature.   By attempting to Convert the tyres, I was able to exit the Sculpt Workspace- resulting in 102 Bodies and Surfaces.   If that is too much of a load for your system, you can move some of the Sculpt Bodies into new Sculpt Features or other Designs entirely- just Copy then Paste.

[mavigogun]

Attached is the design with most of the Sculpt Bodies Converted, if that might be of use to you. 

[l.hayesBQYR8]

I am aware that I was trying to convert all of the bodies at once, but that actually wasn't where i was having issues.

Thank you for directing me to the Repair Body tool, that is a big help. I knew that 68 had issues, i just wasn't sure how to find out which ones, or how to fix them. 

Also, while converting all of the bodies at once isn't usually an issue for me, i will take your advice and apply them as separate features, just to minimize the total load on my system.

One thing that i'm still not entirely clear about is the 'Bad allocation' message. Is that something preventable, and what does it actually mean? Any further insight would be appreciated, but in any case, thank you so much for your effort so far!

[mavigogun]

---

@l.hayesBQYR8 wrote:

One thing that i'm still not entirely clear about is the 'Bad allocation' message. Is that something preventable, and what does it actually mean? Any further insight would be appreciated, but in any case, thank you so much for your effort so far!

---

I haven't been able to elicit the error yet.    If you could record a screencast,  the context might illuminate cause.

[l.hayesBQYR8]

I have attached a screencast of a fairly typical 'Bad Allocation'. 

In the video I am trying to perform a simple 'unweld edge' function, and crease a nearby edge too, but a 'Bad Allocation' occurs somewhere along the line. After that, i lose all ability to use the tools, the rotational navigation only partially works, and edges i select can not be unselected. 

Soon after, the whole program crashes. 

Hopefully this offers some context, which might highlight a cause.

[mavigogun]

Don't just play wack-a-mole with those error reports- fill them out with step-by-step description of the conditions surrounding the crash and what you were doing when it happened.    Combined with the design file, these are the primary tools which enable developers to confront bugs.

[mavigogun]

@Anonymous, this might find quicker response on the Support forum.

[l.hayesBQYR8]

Fair enough, will do.

It's just that when i've filled them in in the past, they don't necessarily produce immediate results like posting on the forums.

Either way, if it means that others won't end up with the same issues in the future, i suppose it's worth it.

Thanks for you help

[gerhard.bedners]

Hi community,

I often had the same "bad allocation" error, thought it's my construction. I couldn't find a solution until I found the same error in a forum for an application to render images. This brought me to the idea that it's a common problem of applications with high memory requirements.

After that I enhanced the memory of my notebook from 4GB to 8GB, and the problem has not occured any more!

Maybe this helps.

Best regards Gerhard