Maya 2017 update 4 Runtime error R6025 -Pure virtual function call

[Anonymous]

Hello,

Animators are constantly getting the same crash for random reasons.

This ranges from clicking a control "nurbs curve" and scrubbing the timeline. Or it could be switching subdivision methods on or off with "1" and "3" on the keyboard. Another reason would be using the "reload textures" option in viewport 2.0 to force the textures to load we have attached to the rig geometry of the characters.

Firstly, it would be great to get a couple of suggestion as to why a runtime error of the "R6025 pure virtual function call" variety would occur.

3rd party tools we are running:

mGear

a custom plugin for the characters' spines

MG Picker for selecting character controls.

Any assistance would be greatly appreciated. Please let me know if I can provide any details.

Thanks.

[sean.heasley]

Hi @Anonymous and welcome to the community!

There's a few potential fixes to this I'll list below.

• Uninstall and reinstall Visual C++ (see How to remove and reinstall Microsoft Visual C++ Runtime Libraries).
• Install the latest update(s) for Maya (right-click the Autodesk Desktop App on the taskbar by the time and choose "Check now"; see also Autodesk Downloads).
• Install the current Windows updates from Microsoft (see Windows is up-to-date).
• Reset Maya to defaults (see deleting your settings/preferences)
  
  Let me know if any of these solve your issue!
  
  Please hit the Accept as Solution button if my post fully solves your issue, or reply with additional details if the problem persists.
  
  Kudos are greatly appreciated. Everyone likes a thumbs up!
  
  

[Anonymous]

Thanks Sean,

We used the all-in-one installer on the link you shared. We have only tested it on one machine so far and the animator had a crash with the same error shortly afterwards  

All the other things you suggested we have done as well to no effect. Is there any other avenues we can try out, we are getting rather desperate. Scores of crashes across the board every day.

Thanks in advance.

[edit: I have a suspicion IT might not have uninstalled all the runtime libraries and then used the all-in-one installer. Will keep you posted Sean.]

[sean.heasley]

Hi @Anonymous

Any luck with the runtime libraries or did they not solve the issue?

[Anonymous]

Hi @sean.heasley,

So far so good, although I would please like to give it some time before I accept it as a solution. I will check in in a couple of days time and reply if this particular crash has been resolved.

Thank you for your help and for following up.

[Anonymous]

Hi @sean.heasley

The crashes seem to have become less since the visual c++ redistributables fix but we are still getting the same pure virtual function call error regardless, I'm sorry to say.

[info]

After reading on the max forum there was a problem with the WACOM tablet, AND suffering similar issues, I pulled the usb of my wacom and the problems were gone! ( this was on Maya2016sp6 Windows7 )

[Anonymous]

@info thanks but sadly this did not work for us. @sean.heasley We are still losing hours of work collectively every day with this particular crash and the triggers are completely random.

[info]

For us the steps to make the problem go away were ( as suggested by AD support ) :

- update windows7 runtime libraries ( in my case I just let windows update run until there was no update left )
- update the graphic drivers ( in my case Nvidia )
- update the wacom drivers.

In between the steps I restarted the machine.

Now I am able to work with a wacom and have no longer the -pure function call error in maya
( which were so severe that in some scenes I could not select even an object without an error ) Hope you get it solved soon.

[sean.heasley]

Thanks for the tips @info!

@Anonymous be sure to try what he posted! I'm passing this case around through our support channel so hopefully we can find some other potential solutions if what was suggested doesn't work.

[Anonymous]

@sean.heasley I was wondering; is there no way to setup Maya to output into a .TXT log on disk saying what node or action was run last before the crash happened? At the moment it's virtually impossible to figure out what is triggering the crashes without a smarter way of logging all the evaluations that happened when the pure virtual function call occurs. If we can set this up we can narrow down on the possible culprits.

[sean.heasley]

Hi @Anonymous

By default Maya should create an error file (MayaCrashLog[yymmdd.hhmm].log)

Here's some steps you can take to make sure the crash report is being made.

[Anonymous]

@sean.heasley Thanks for this, I never knew about those log files. The problem is that Maya does not see this pure virtual function call error as a fatal crash and thus it doesn't write a log file. Any other way the AD support crew perhaps knows about that I can make Maya more verbose?

[Anonymous]

@Anonymous, in your animation files there`s any aux effector in control rig?

I`m suffering this same issue, just after I start to use this tool in my scene.

[Anonymous]

@Anonymous Sorry I'm not sure what you mean with "aux effector"? Would you mind defining what exactly that means?

[sean.heasley]

Here's a break down on aux effectors.

[sean.heasley]

Hi @Anonymous any changes with this issue?

[sean.heasley]

Hi all!

I talked to another team member and he had this to say

"A pure virtual call for Maya is normally seen when an object has been deleted and then accessed later.

For a developer who can reproduce the issue one would set a breakpoint on the _purecall and then check to see where its coming from to know where to look.

For a customer they hopefully should be able to also set the breakpoint. For Maya 2018 I believe we have finally put up the stripped Maya debug symbols onto the Autodesk Symbol server for customers to access.

If there is a Windows dialog box up at that point you should be able to use Visual Studio IDE to attach to the Maya process and see if there is a stack trace that could be used."

Let me know if anything changes!

[Anonymous]

Hi Sean I work with Marthinus. We are using maya 2017 can you make those symbols available too? 

Could you provide a link to them please, I don't know where the symbol server is.

[sean.heasley]

Hi @Anonymous

I talked to my co worker again and he was wondering, is it possible for your team to make the switch to Maya 2018?

We have a semi-automated method in place now with 18 and its possible this issue may not even present itself in 2018.

If you can't/don't want to upgrade we can still troubleshoot this for 17.