MM requesting more GPU memory

MM requesting more GPU memory

Anonymous
Not applicable
6,053 Views
18 Replies
Message 1 of 19

MM requesting more GPU memory

Anonymous
Not applicable

I am getting crashes with MM, associated with video memory.

screen shot attached.mmcrashednvidia.PNG

 

message pops up from my Nvidia OpenGL driver:

An application has requested more GPU memory than is available in the system. 

The application will now be closed.

Error code: 6

 

MM obviously uses a lot of GPU memory, but now I'm unable to complete a project because of this constant crash. It happens randomly during certain operations. Currently it keeps happening during a magnet brush session to clean up some mesh edges. 

 Files I'm having issues with are in range of 3 million to 7M triangles.

 

screenshot of my task manager as dedicated and shared gpu memory gets filled up while MM running.

mmgpumemory.PNG

I'm running this on a boxx workstation with 64GB RAM, Quadro P5000 with driver 411.95. Had same issues with 411.63.

Any help appreciated. Thank you,

Robert

0 Likes
6,054 Views
18 Replies
Replies (18)
Message 2 of 19

Anonymous
Not applicable

I'm having the same problem here. 

Quadro P1000 and 32 GB of RAM. I only notice the RAM is completely filled up when encountering the fault.

And by monitoring while working I discovered that every operation adds to the RAM usage, like rotating, filling and remeshing. When the operation is done the memory usage doesn't drop until I closed Meshmixer and restarted.

Not ideal to get things done.

Hopefully we can find an answer. 

Thank you,

Loren

0 Likes
Message 3 of 19

Anonymous
Not applicable

I'm adding my voice to this as I'm running into the same issue with 16GB of RAM and a Quadro P1000 with 4 GB.  I tried installing new Nvidia drivers and even removing some background applications to slim down resources.  Still getting the issue.  Any help from Autodesk?

0 Likes
Message 4 of 19

Anonymous
Not applicable

No Autodesk guy... seems they are missing here...

Did yo try MM 3.3 instead of 3.5 ? (pretty same functionality but the ViewCube and .3mf support)

 

0 Likes
Message 5 of 19

hybrid_87
Explorer
Explorer

I'm having the same issue. Did anyone find a solution? 

0 Likes
Message 6 of 19

Anonymous
Not applicable

No solutions yet. MM still crashing on me dozens of times per project.

0 Likes
Message 7 of 19

Anonymous
Not applicable

What about drivers for my nvidia p5000, anyone know of a driver that is not crashing maybe? I've tried old and the newest, same problem. MM requesting more gpu memory than available. Card has 16GB memory.

0 Likes
Message 8 of 19

Anonymous
Not applicable

I'm running a TitanX on my Mac without any issues (using NVIDIA Web Driver 378.05.0525f16) but that's a different thing...

 

Just saw that there are two versions available for Quadro GPUs:

  • Optimal Driver for Enterprise (ODE) Most users select this choice for optimal stability and performance. 
  • Quadro New Feature Driver (QNF) Users occasionally select this choice for bug fixes, new features, new VR headset support or new Game Engine support. 

Did you try the QNF?

0 Likes
Message 9 of 19

Anonymous
Not applicable

Hey Gunter,

No I haven't tried the QNF yet. Will give that a shot. 

And I've been hesitant to back version to 3.3 and lose the view cube. If i do that, is there a quick easy way to get orthogonal views (top, front, right, etc..)?

0 Likes
Message 10 of 19

Anonymous
Not applicable

Well, switching between perspective/orthographic view can be done without any problems via the View menu in 3.3 as well.

Standard views: You need to enable Snap (most left button in the Hotbox). That done, as you navigate/rotate the scene the cam snaps to a standard view as soon as you come near to it (Note that enabling Free, the second icon in the Hotbox, overrides Snap). Maybe this needs some training, but it's still my preferred way to set a standard view...

Another way to get specific views and store certain views is to use mmApi (know it's a bit complicated to set it up....). In  pre-ViewCube times I wrote a script to do this, but as soon as you navigate in MM again, the cam snaps back to its previous position. If you're interested I'll post it. In my MM Tool Manager V3  (message 35) this storing of views is implemented as well.

---

Downgrading isn't that big deal. All personal stuff you did (parts, stamps, shaders, printers...) should stay (but to be sure make a backup of the meshmixer folder in your documents).  So I'd give it a try... but looking at your advanced GPU I guess it's another problem...

----

Another thing you could try (assuming MM is down - as it crashed):

There are different issues if no printer is set. So check meshmixer.ini

That file is located at:

Windows: C:\Users\User Name\AppData\Roaming\Autodesk\meshmixer.ini
(NOTE: AppData is hidden by default, so you might have to enter that path manually or choose to show hidden files.)
Mac: ~/.config/Autodesk/meshmixer.ini

(NOTE: .config is hidden by default, so you might have to enter that path manually or choose to show hidden files.)

 

Open it in some text editor and search for the line starting with "SelectedPrinterUUID". 

If it doesn't exist add this line in the [Options] section:

SelectedPrinterUUID=34043662-242b-4c92-8af7-a38ee78fd995

Or if there's no such ID set put in the ID after "="

(This is the Autodesk Ember - just to set one...)

---

If this still fails another try:

set:

EnableBasicRenderingV3=false

to

EnableBasicRenderingV3=true

This is a worst case solution but interesting to know if that works.

---

I'm so sorry if all this trial and error. But it seems technical support for MM is limited Smiley Wink

 

 

 

 

 

0 Likes
Message 11 of 19

hybrid_87
Explorer
Explorer

Thanks for the help Gunter.  My particular issue, which seems to be the same as the others here, is with a Quadro p1000.  Meshmixer will start okay, but simply moving the view around or doing simple tasks like selecting triangles will eventually fill my RAM and crash the program.  I then get the same error screen as shown in OPs post.  I've logged a query with Nvidia too, hopefully they will assist.  I have tried rollig back to 3.3, and disabling all fancy rendering options and I have a printer set, still the same issue persists. 

 

I haven't tried the QNF drivers yet, its a work laptop so will give it a go when I can get the admin password to update the drivers and let you know if I have any success.

0 Likes
Message 12 of 19

Anonymous
Not applicable

I put in a ticket with Nvidia  back when I first posted this, and even spent time on the phone with them, they were absolutely zero help. Blamed the problem on MM.

0 Likes
Message 13 of 19

Anonymous
Not applicable

Seems like going back to v3.3 may have solved it. So far gpu memory is not filling up like it was before, and thus not crashing the card and my system like before. Fingers crossed.

 

0 Likes
Message 14 of 19

Anonymous
Not applicable

@Anonymous 

I'm not sure about what is happening with the meshmixer.ini file doing a downgrade. At a upgrade the values of the previous version are kept and new ones are added.

Recently I did a downgrade to a MM 2.x version to track down another issue and I got rendering issues with the .ini formerly written by 3.5. So maybe its a good idea the create a fresh one in your case. Simply rename or move it (to keep a backup) while MM is down. On its next start MM will create a fresh one without 3.5 parameters.

0 Likes
Message 15 of 19

Anonymous
Not applicable

Yah I created a new .ini

Unfortunately I got the crash again, error 6 from nvidia gpu, application requesting too much memory.

For a bit there I thought all was good. It has been better though so going back to 3.3 has def helped.

0 Likes
Message 16 of 19

hybrid_87
Explorer
Explorer

I tried a clean install using the latest QNF driver package from NVIDIA and MM 3.3, along with all updates from Dell.  Seems like that has mostly worked for me.  RAM doesn't seem to be filling as fast or irreversibly as before.  Only prelim tests but I'm optimistic.  I want to try MM 3.5 again but can't seem to get it to install ATM.  I'll report back if things go awry again. 

0 Likes
Message 17 of 19

hybrid_87
Explorer
Explorer

Scratch that, spoke too soon. Still crashing.  How very frustrating.

 

My solution for now is to disable the graphics card all together and use the onboard graphics.  A bit slow but at least I don't crash the program every 5 mins.

0 Likes
Message 18 of 19

kurt
Observer
Observer

I have a Quadro K2200 with this same issue. 

442.92

 

3.5.474

 

A solution I have found:

Nvidia Control Panel->3D Settings->Manage 3D settings->Global settings

Set to the 'Autodesk Maya Legacy' Preset 

 

This has eliminated the climbing GPU memory usage problem and eliminated the crashing.  I don't know which setting it was in that preset that fixes the issue and I haven't tried all the presets either.  Their may be others that would work. It would probably be smart to make a preset just for MM instead of a global one. 

 

 

Message 19 of 19

K.Nikolov89
Community Visitor
Community Visitor
This resolved the issue for me!

MM 3.5.474, RTX A3000 with 6gb dedicated and 15.8gb shared.
Used to fill up in a couple of minutes on a 200k triangles model.
Now with "Autodesk Maya Legacy" preset is doesn't fill up even 1gb of Dedicated
0 Likes