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

[Anonymous]

We have an issue  any ideas?

[janelson33]

This is technically a solution, for any of us using the 3DConnection mouse, until they can address the mechanics of the software, saved my butt.

I'm going to ask my boss about a graphics card update to one of the certified units. Several computer manufacturers make PCs which are CAD graphics certified (HP Z2 G3 being one example) so it might be one aspect we all need to have corrected before we can really start moving on from there. You wouldn't drive you car with a flat tire and expect good performance, same premise applies here I'd think. Is that thinking somewhat correct @johnsonshiue @Mark.Lancaster?

[Anonymous]

Same problem here.  Spacemouse allowed me to save my work.  I don't believe it's a coincidence that I update my monitors yesterday to a higher resolution and I've never seen this error before. 

[johnsonshiue]

Hi! Are you able to reproduce the error persistently?

Many thanks!

[Anonymous]

I have not been able to reproduce the error.

[Anonymous]

I think they must have stopped progressing Inventor as a CAD Program. I used to defend this CAD program but after being off it for 5 yrs, it has a real "Cheap and Nasty Feel" about it... same old glitches and work arounds.

Very disappointed!!!!! Put some resources back on Inventor and do some catch up, the opposition is leaving you behind.

[johnsonshiue]

Hi Rip,

Were you able to reproduce the error? If yes, could you share the steps with me ([email protected])? Regarding your comments, you are entitled to your opinion. Your comments can be interpreted in many ways (ranging from benign to offensive). Do you mind starting a new thread and sharing your specific examples? Inventor as a CAD tool, is far from perfect. There is a lot of room for improvement. I would like to understand specific issues. So far, I am not seeing anything actionable yet.

Many thanks!

[Anonymous]

Hi Johnson, Anywhere there is a work around there is an opportunity for improvement.

Work Around = Cop Out.

[johnsonshiue]

Hi Rip,

Totally agreed! Workaround is like exception to the rule, the last resort before code change. There should not be many workarounds. If they are, we have problems. Like I said, there is always room for improvement in Inventor. One can pretty much say the same for every product.

If you could, please start a new thread and list the most annoying workarounds. I would like to understand them better and work with the project team to see if we can remove the workarounds. I cannot promise that all workarounds are changeable or removable. But, I do understand workarounds are exceptions and they are not norms.

Many thanks!

[janelson33]

Graphics cards do not help this software FYI, I learned that after this post.

https://www.youtube.com/watch?v=OnOtGrX_dBk

2019 only just started supporting full use of multi-core processors. I just got my new computer installed with the recommended spec from Autodesk (fast processor, 32 GB RAM) and the larger assemblies are already improved. I haven't messed with 2019 too much, but it seems like a capable computer can reduce some of these computing glitches.

[n.schotten]

Interesting results!

As for multicore support. IV did allready, however mostly for rendering and more recently for some of the simulation work. They have steadily increased the multicore support over the years.

Bit of a problem i have with Inventor (and most other sw) is that the recomended hardware be an i7 CPU. But never state what generation it should be. I'm pretty sure a gen 1 i7 will not do as well as a gen 8 at the same clockspeed.

But this all not withstanding, the 8bit issue could still be an nVidia/MS driver issue.

[johnsonshiue]

Hi Jarott,

It is not true that Inventor 2019 just starts to support multi-threaded and multi-core operations. Inventor has been partially multi-threaded and multi-core for quite a few years. Below is a list of supported operations.

https://knowledge.autodesk.com/support/inventor-products/downloads

Many thanks!

[b_sbr]

Good one! Moving the model while pressing [Esc] got rid of the message here. Thanks for the tip.

As mentioned above, problem also seen on 2018.

[Gabriel_Watson]

@johnsonshiue: After some investigating, I have more information about this that could be helpful to isolate the issue.
This error popped up a few times (while different assemblies were open) in one of the fastest laptops we have here. And ONLY on this machine!

The difference between this laptop and other PCs seems to be hiding in the fact that this integrated video card above (Intel HD Graphics 530) does not have dedicated video card memory. It's allocation on the PC's RAM might be causing this hiccup.

[johnsonshiue]

Hi Gabriel,

Many thanks for sharing the information! I suspected it was hardware related but I did not have any proof. Nor are we able to reproduce the behavior. The system requirement does call for dedicated graphics card. Integrated graphics system can be used but we are seeing mysterious issues. It is better to have a dedicated graphics card. Also make sure Inventor utilizes the graphics card.

Thanks again!

[Gabriel_Watson]

If the error message could say that instead, once confirmed this is the problem, at least we would be able to blame the user for not heeding that fact.

[n.schotten]

As far as i can tell it happens on systems with CPU based GPU's in conjunction with discrete GPU cards.
And so far as i know on systems with nVidia (quadro) cards.

And with IV set to use the discrete card for it's graphics.
But i also think it has to do with the materials. As in the look (texture, colour etc) of the materials. As if the texture mapping memory space is a problem. It may to do with the 'rendering' settings of the UI i think. Why else would even the slightest change in model orientation end the memory issue.
I propose that an inquery into the settings could help to identify where things go wrong.
- system (CPU,GPU, RAM of both); Video driver version, IV version, that kind of data.

- UI 'render' settings.

- UI background

- Materials in the file when it showed the error. Stock material or from your private material library.

- Were parts set to not visible or suppressed at the time.
-?

The error does not crash IV, so there is no crash report data to sent to Adesk for review. So we have to report it ourselves. It might be a loss of face to ask about this issue in a news letter or AUGI edition. But these questions should be easily found when one looks for the 8byte error in Google/Bing/... So we might get others to file their system data on this problem in hopes of getting the Autodesk engineers to get a better handle on it and work on a fix.

Niels

[n.schotten]

The problem persists in IV2019.1 (build 200). My co worker had the issue pop up last week.
He got around the problem by trying to save (ctrl-s) between error pop-ups.

So apparently that also works to end the 8byte bug.

[frank.gavilar]

Had the same problem for the first time on one of our machines today. Assembly with about 500 instances and a few other tabs (Assembly drawing, Part, and Part drawing). Nothing out of the ordinary for our workflow. Inventor used about 1,8 gigs of memory.

System specs:

• Intel Xeon E5 2620 @ 2Ghz
• 16GB of ram
• Nvidia Quadro 4000 descrete graphics card
• 1tb of SSD storage.

Running Inventor 2019.1.1

%temp% folder size is 51 GB but the temp folder on a similar machine is 86 GB.

[neljoshua]

I just got this error. Fortunately nothing is lost.

I am running Inventor Pro 2019 on a Macbook Pro. My Mac does have a discrete graphics card, but it automatically switches between integrated and discrete graphics. I just turned this off and forced it to use discrete graphics all of the time.

[Frederick_Law]

See if this helps:

Set swap/page file min and max to 48GB or 64GB.

This fix a SW out of memory problem.