Announcements
Attention for Customers without Multi-Factor Authentication or Single Sign-On - OTP Verification rolls out April 2025. Read all about it here.

Parts keep getting corrupted - huge file size

JonathanFWorkAccount
Contributor

Parts keep getting corrupted - huge file size

JonathanFWorkAccount
Contributor
Contributor

I have a part which is causing me major issues. Recently it has caused Inventor to freeze up and use 100% of my available RAM trying open/save/update files, but never stops loading.

 

I deleted the part and remade it, which worked... temporarily. The same thing happened again, so I think it's more to do with how I'm using the part than the part itself being the root of the issue.

 

I will explain how I'm using this part. I'm not able to share the whole tree of models due to confidentiality.

  • I have a master part model, with a few different solid bodies.
  • I have derived a part from one of the solid bodies (this is the problem file).
  • I have then used that part in an assembly which is the assembly which goes on my drawings.
  • Then I have derived a part from that entire assembly to use for my FEA experiments to see how it performs. This lets me easily fill in any gaps with material, and modify the parts slightly in preparation for the FEA to run, which is why I don't just do FEA on the assembly file.

I have been going back and forth running the FEA and then modifying the master part, updating the FEA model and running it again. This works for a few times but then for some reason it gets corrupted at some point, and as you can see from the attached part file, its file size is huge (550 times the size of the other parts I made). In fact, it's nearly at the limit for what this forum allows to upload (55 MB out of the 71 MB allowance).

I have sunk a lot of hours into this to no avail other than identifying that the part file size seems to be part of the issue. My suspicion is that maybe when updating or saving the FEA file, it modifies and corrupts the part(??)

 

Is anyone able to find what all of the storage is being used for - why is the part so unnecessarily large?

Is there a way to avoid this happening?

 

Thanks!

0 Likes
Reply
504 Views
8 Replies
Replies (8)

rogmitch
Advocate
Advocate

I was looking at this very issue a few days ago.  I model almost exclusively using multi-solid bodies.  I noticed that for one particular project some of the file sizes were much larger than I would have expected for the complexity of the parts.  The parts for that project typically have 50-150 solid bodies and a few derived surfaces but some file were in excess of 80 MB.  

 

Quite by chance,  I found that if I rolled the EOF to the top of the tree, saved the file then rolled the EOF back down and re-saved , some files were reduced in size by over 50MB!  I have no explanation as to why this reduction occurred but it seemed to work for most parts in the project . 

 

May be worth a try.

 

Roger Mitchell

0 Likes

JonathanFWorkAccount
Contributor
Contributor

That was a great idea, but unfortunately this didn't work for me. I tried saving the master part and derived part both with EOP at the top then at the bottom, with no luck.

In fact, I even just tried completely deleting all features, as well as the materials used in the part, and saved it as an empty part. Still 55 MB! Bizzare!

0 Likes

sundars
Autodesk
Autodesk

Hi @JonathanFWorkAccount 

 

I took a look at your part. It's got a derived part in it which seems to contain some enormous hole data. Somehow deriving that model also brought in a whole bunch of information along with the original part. As an experiment, you could try deleting some of those hole features (or atleast suppress them) and try re-deriving or updating your existing derived part. And add the holes as a post-derive feature.

 

I did export the file as a STEP file and it produced a fairly compact file. 

 

If you have the original derived source, please add that here and I can take a look at it to see what's contributing to the data bloat.

 

Thanks

-shiva

 

Shiva Sundaram
Inventor Development
0 Likes

rogmitch
Advocate
Advocate

It is a shame it did not work and I agree it is bizarre to still have 55MB with an empty file.

 

In my case I believe the excess file size is related to the derived parts.  I often find that if I derive a single solid body from a part with say 100 solid bodies that the the receiving file size will increase by a significant proportion of the file size of the base component which could be many MB.  It may be that this is just the way it has to work but it does not help to keep models light and nimble!

0 Likes

JonathanFWorkAccount
Contributor
Contributor

Hi Shiva.

 

Thanks for taking a look into my issue.

Would it be possible to share the source files privately - is there an email address I can send them to or something?

 

My master part actually has solids in it which is derived from a customer model (STEP file).

jfowler_0-1646675630568.png

It certainly has a lot of diameters in it which might be an explanation for such large hole data.

I can try some experiments tomorrow to see if I can get the part file size down with some modifications around those bodies.

 

0 Likes

sundars
Autodesk
Autodesk

@JonathanFWorkAccount I just saw your post about deleting all features and still having a file size of 55 MB. That sounds like a persistent leak. If you can post the original file (empty or with features), we can take a look.

 

Or you can email it to me: sundarsATautodeskDOTcom

 

Thanks

-shiva

Shiva Sundaram
Inventor Development

sundars
Autodesk
Autodesk

@JonathanFWorkAccount 

 

You can email me the files: sundarsATautodeskDOTcom

 

You said, it was originally created from a step file. please also include that if possible. You can zip them up and send them to me and if its too big, perhaps you can put it on some shared cloud drive and give me access.


Thanks

-shiva

Shiva Sundaram
Inventor Development
0 Likes

sundars
Autodesk
Autodesk

Hi @JonathanFWorkAccount 

 

Thank you for sharing the corrupt files. @Anonymous and I are experimenting with it. We see the corruption which is a fairly big leak. If you have steps to reproduce the corruption that would go a long way to figuring out the root cause. 

 

Thanks

-shiva

 

Shiva Sundaram
Inventor Development
0 Likes