no more memory is available - attempt to allocate 8 bytes of memory failed

[Anonymous]

We have an issue  any ideas?

[mdavis22569]

upgrade to 16 gigs?

Also maybe close some of the files so you don't have so many things going on..

from just a quick look at your jpg ...3 assemblies, 2 idw's.  Not sure how big all of the assemblies are from the pictures or what's calculating etc.

Just open the one idw, and from there open the iam or ipt associated with it.

Just my opinion

Mike 

[-niels-]

Welcome to the community!

Not sure if this is helpful in any way since it's an article for inventor 2010, but it might be useful:

https://knowledge.autodesk.com/support/product-design-suite/troubleshooting/caas/sfdcarticles/sfdcar...

[Anonymous]

thank you for replying, i use a lot of windows in the same time, some time i use solidworks autocad mech and inventor on one computer. Whatever i'll try your advice 

thank you again

[n.schotten]

This problem persists even in Inventor 2018.2 (or so).

System has plenty of ram left. Inventor only uses ~3.8gb of ram.

The error window won't go away.

This is BS! Get your act together Autodesk developers!

It's not a real ram issue. There is a bug somewhere. This issue seldomly pops up, but i have had it happen 3 or 4 times since migrating to 2018.

Different workloads, i have had IV use far more memory without issues.
Could be a graphics memory issue, but the current iam doesn't have all that many/dificult colors/textures to deal with. And i'm on an nVidia Quadro P4000.

[mdavis22569]

Hi @n.schotten

How big is the file? 

I'm not experiencing with 5000 plus part assemblies ...

What do you have in your Task Scheduler?

[n.schotten]

Hi,

The iam only had 1095/611 items/parts.

It does seem like it was a graphics issue. as soon as i tried to manipulate the view with my 3dconnexion, whilst holding down the esc key to speed cycle trough the recurring error popup, as soon as the view moved a bit the error disapeared.

And i wasn't looking at the task scheduler but at the windows task manager. as said. plenty of RAM still available.

And as i'm working now, IV uses 4.1gb...

[Anonymous]

Memory is one thing, how it is used (abused) is something else. It takes 10 lines of programming to crash windows by claiming all the memory and resources and not releasing them. Look up GDI-objects. They are entry points into the windows machinery, to give a simple explanation. Windows gives a default number of 10000 objects to a program. As I am writing this I have an Inventor open with no files opened and task manager says that Inventor has 5980 GDI-objects. Pretty close to 10000 without anything going on, if you ask me. The next program in the list is Outlook having 913 objects. So here is a reason why you can have plenty of memory and yet no room to work.

[johnsonshiue]

Hi Niels,

Based on your description, it sounds like a file-specific bug to me. Have you sent us the files? If not, could you share them with me ([email protected])? I would like to understand the behavior better.

Many thanks!

[bullit2312]

I've have this exact same issue a few times, (once again this morning).

Thanks for sharing your solution using the 3d mouse it forced the error away, nice tip.

[b.graaf]

Today we have received a support call from one of our customers and she has the exact same error message:

no more memory is available - attempt to allocate 8 bytes of memory failed

She also has enough RAM. It must be some kind of bug somewhere!

It is also Inventor 2018, I only don't know which SP at the moment....

[Mark.Lancaster]

@b.graaf

After exiting Inventor have the user clean out their personal temp (%temp%) folder.  Delete as many files and folders as possible.  You'll not be able to delete all files and folders but clean out as much as possible.  Restart Inventor, does that resolve the issue?

[b.graaf]

Hello Mark,

Thank you for your quick reply.

I will ask her to do that and let it know if I have any new information.

[jweiss1313]

Hi Mark,

I just had a guy who had the same error message.  He had to kill Inventor and then cleared his temp folder.  Wish I would have seen the tip about hitting the ESC button while rotating with 3D mouse.  He was unable to save and had to kill Inventor.

I'm not buying that clearing the temp folder fixes the problem.  This is a long outstanding problem (8 years) that someone at Autodesk should look into and address.  I guess it doesn't happen enough to be worked on.

Oh well, I just thought I would update the thread to keep this issue visible!

We are running Inventor Professional 2018.2 on Windows 10

Nvidia Quadro M5000

32 GB RAM

[n.schotten]

@Mark.Lancaster The problem with this error is that it is not replicatable in a discribable way. There is no step-by-step for it.

So cleaning out the temp and try again.. it won't give you the error again, as soon as you start working on the 'affected' file.

These errors can happen 2-3times in a day or not for weeks. It does seem that setrain files are more prone to generating this error than others.
And it looks like it has something to do with graphics and some material color styles assigned to parts/faces. So something to do with texture map memory room or something along those lines. Not sure if it happens only with nVidia GPU's. it happens on my new Quadro but also on the nVidia 'game' GPU on our other system.

I also came across an other bug... switching from the design project to the library project (to edit a lib file) and then back to the design project, the material and appearance libraries are empty. I need to restart IV to get the material lists back.
I hope to be able to make a screencast of it sometime this week and post it in the bug report department.

[Mark.Lancaster]

@jweiss1313 and @n.schotten

A few users have reported this issue in the forums the past couple of weeks.  It appeared cleaning the personal temp folder had resolved their issue for those users.  It is the solution..  Not sure..  But I will tag @johnsonshiue for his input to see if there are other things that may help. 

Also in earlier version of Inventor, this message appeared when there was something wrong with projected geometry in your sketches.  I don't think this is the reason but also in the past it was recommended to install process explorer https://docs.microsoft.com/en-us/sysinternals/downloads/process-explorer and launch the product when the message appeared to see what process was stealing all the memory.

@n.schotten

Also your issue with your project file may point to a corrupt project file.  When you start seeing stuff like that its just easier to create new ones from scratch.  Anyhow my 2 cents..

[johnsonshiue]

Hi Mark,

The error may not be triggered by the same cause. I think most of the times it is indeed due to running out of space in %temp%. It is because users may not be aware that %temp% is being used and files are not cleaned up. It is also possible that there is memory corruption leading Windows to believe not enough memory is available. I will need to see a reproducible case in order to tell.

Many thanks!

[Anonymous]

It would be worth the trouble if those of you experiencing the problem would check "GDI-objects". It can be set visible by choosing this column in the view settings of task manager. When "googling" GDI-objects", "CAD" and "memory" you come across other software experiencing memory problems. And GDI-objects being mentioned. Further digging in the subject learns that a program gets 10000 objects as a limit. Also that it is not normal that it runs in the thousands and warnings could pop up from 60% use up. I rarely see Inventor in my taskmanager using less than 6000 GDI-objects, so it might be worth checking this if you actually get into trouble.

[jweiss1313]

Alex,

Thanks for your feedback.  I will check this the next time I see this error in my department and I'll update the thread on what I found.

Also Thanks to Mark and Johnson!

[n.schotten]

Next time aks the users to check the %temp% map size before emptying it. As well as drive space total/available and RAM size...

And it would sound like a simple way to check if the temp realy is the/a culprid. Just dump a s*it load of data into it and see what happens.

But as i found that working the view orientation during the error seems to resolve the error, it sounds to me that is has to do with video/graphics memory allocation.

Niels.