Mayapy 2025 crash with *NodeEditorSavedTabsInfo nodes

Mayapy 2025 crash with *NodeEditorSavedTabsInfo nodes

sophie.chauvet
Explorer Explorer
235 Views
2 Replies
Message 1 of 3

Mayapy 2025 crash with *NodeEditorSavedTabsInfo nodes

sophie.chauvet
Explorer
Explorer

Hello, 

 

We had issues using maya 2025 on our productions. 

The issue is a crash that occurs when opening of a scene (using mayapy and mayabatch only) that contains two references of the same file, where that file contains "*NodeEditorSavedTabsInfo*" nodes.

 

Opening the scene in GUI works fine, and does not cause a crash.

 

I have performed tests with a vanilla Maya installation (no plugins) for both Maya 2023 and Maya 2025, and the problem only occurs with Maya 2025.

 

Steps to reproduce : 

- create a cube in a cube.ma file in maya 2025 

- create a new file referencing cube.ma twice. Save it in assembly.ma

- use mayapy to open the assembly.ma file in python

- scene will crash at opening

 

Code used in mayapy to open the file : 

 
import maya.cmds as mc
from maya.standalone import initialize
initialize()
fp = r'D:\assembly.ma'
mc.file(fp, open=True, force=True)

 

Scene is also crashing on farm with maya batch.

By debugging the Maya ASCII file, I was able to identify that these lines in the referenced cube.ma file are causing the bug:

 

 

connectAttr "pCubeShape1.msg" "MayaNodeEditorSavedTabsInfo.tgi[0].ni[0].dn";
connectAttr "pCube1.msg" "MayaNodeEditorSavedTabsInfo.tgi[0].ni[1].dn";

 

 

Which lead me think maya can't connect twice these attributes without gui anymore.

With the exact same lines, its working in 2023.

 

Stack trace : 
Warning: Unrecognized node type for node 'hyperShadePrimaryNodeEditorSavedTabsInfo'; preserving node information during this session.
Warning: Unrecognized node type for node 'MayaNodeEditorSavedTabsInfo'; preserving node information during this session.
Stack trace:
ntdll.dll!KiUserExceptionDispatcher
DependEngine.dll!Tplug::addToNet
DependEngine.dll!Tplug::copyFlags
Shared.dll!TduplicateCmd::copyPlugFlags
Shared.dll!TduplicateCmd::duplicateSceneFileNodes
Shared.dll!TduplicateCmd::duplicateSceneFile
Shared.dll!TglobalTranslator::doReadFile
Shared.dll!TfileUtil::readFile
Shared.dll!TfileReferencer::readReference
Shared.dll!TfileReferencer::reloadReference
Shared.dll!TfileReferencer::loadChildren
Shared.dll!TglobalTranslator::doReadFile
Shared.dll!TfileUtil::readFile
Shared.dll!TfileReferencer::readReference
Shared.dll!TfileReferencer::reloadReference
Shared.dll!TfileReferencer::loadChildren
Shared.dll!TglobalTranslator::doReadFile
Shared.dll!TfileUtil::readFile
Shared.dll!TsceneOperator::openFile
Shared.dll!TfileCmd::handleFileOpenFlag
Shared.dll!TfileCmd::handleFlags
Shared.dll!TfileCmd::handleFlags
Shared.dll!TfileCmd::doCommand
CommandEngine.dll!TpythonInterpreter::dispatchMayaCommand
CommandEngine.dll!pythonDispatchMayaCommand
Shared.dll!TfileCmd::clearRefHierarchies
python311.dll!_PyObject_MakeTpCall
python311.dll!PyObject_Vectorcall
python311.dll!_PyEval_EvalFrameDefault
python311.dll!PyMapping_Check
python311.dll!PyEval_EvalCode
python311.dll!_Py_SourceAsString
python311.dll!_Py_SourceAsString
python311.dll!PyThread_tss_is_created
python311.dll!_PyRun_SimpleFileObject
python311.dll!_PyRun_AnyFileObject
python311.dll!PyDict_DelItemString
python311.dll!PyDict_DelItemString
python311.dll!Py_RunMain
python311.dll!Py_RunMain​

 

EDIT: just a precision : I've tested various namespaces (foo / bar or foo and foo1) on the two refs, it's not solving the problem.

 

Versions tested :

Autodesk Maya 2025.3

Autodesk Maya 2023.3

 

We ended up deleting these nodes to avoid the crash. Is there another solution?

 

Thanks.

0 Likes
Accepted solutions (1)
236 Views
2 Replies
Replies (2)
Message 2 of 3

brentmc
Autodesk
Autodesk
Accepted solution

Hi,

This is a known issue that was addressed in Maya 2026.2:

MAYA-137713: Mayabatch crashes when nested referencing a scene with MayaNodeEditorSavedTabsInfo

 

Brent McPherson
Principle Engineer
0 Likes
Message 3 of 3

sparrishDHAXD
Observer
Observer

Could we get a fix for this in 2025?

0 Likes