2024 so disappointing

[Ιάσονας]

can't speak for everyone but 2024 is probably the most unstable release of maya ive ever seen,

svg file i disable it from both check boxes, will load up next reboot,

doing booleans crashes,

changing rederer view crashes,

lots more of problems

maya 2023 was prone to crashes, why can't you just stick with one version of maya and work on that, why release an unstable version year after year

i went back to maya 2020 used it for over and 1hr hasnt crashed

macos monterey

2.3ghz i9 8 core

32gb ram

8gb video card

[Ιάσονας]

prior to the crash in 24.1 i was in the plugin manager, closed it then closed maya thats when it hung before it crashed

maya 2020 the svg won't load again after unload it,

accessibility full disk access allowed for maya,

i just dont get why everything works well for maya 2020 and not 2024.1

are you running ventura or monterey?

[andrewsilke]

Yes, last week I sent the scene to Nelson via email with the repro steps as per the pm.

I've now upgraded to 2024.1 and NVidia drivers are the 2024 recommended, and I can still crash that scene in less than 10 mins. Mostly multi-cut and duplicating simple objects. 

I am crashing on much simpler scenes too. 

One thing I've noticed is before the crash Maya starts to lag a little.  For example if you duplicate a simple object and it freezes just a touch before completing the duplicate, in 2023.3 it doesn't have this lag.  Anyways it has this slight lag for a while and goes a couple of minutes and then the crash. 

This reminds me of a similar issue I was having in 2023 where I was advised to turn off Preferences > Animation > GPU  Override.   I've just checked my 2023 where everything was working and that is off. So will try that next. 

Turning off "GPU  Override" in the Preferences solved a lot of my 2023 issues btw.   Maybe my Geforce 1080 doesn't like that new setting. Trying that now. 

[andrewsilke]

No, unfortunately, the "GPU Override" off didn't help.  I cashed the scene in about 40 secs. I'll record a video so you can see exactly what I'm doing. Will do that later as I have to head off. 

[andrewsilke]

Here's how to reproduce the crash in my scene, multi-cut, bevel, multi-cut, duplicate. The scene has been sent to Nelson at AD. I'll email him again. 
https://www.youtube.com/watch?v=zHVimroHRIM

But I'm getting loads of crashes doing all sorts of things, this one is just selecting objects and tumbling. 
https://www.youtube.com/watch?v=7XEkJmuAR8w

Crashes without any third-party tools running as well. 

[Ιάσονας]

maya a crash log will indicate whats going wrong,

[syracoj]

I'm on Big Sur but I can check on a different machine with a more updated OS but it won't be an intel mac it will be an m1 mac.

[syracoj]

yes, a crash log would be useful.
If it crashes fill out the CER report (include your email address and a brief description as to what it was that you were doing) then either send me the crash error report number or your email address and I can look it up.

Alternatively, you can open up a terminal and start Maya from the cmd line via by typing in the terminal:

/Applications/Autodesk/maya2024/Maya.app/Contents/MacOS/Maya

When it starts up, use it and when it crashes a stack trace will be populated in the terminal. You can copy/paste that stack trace here.

[Ιάσονας]

Are you running big sur as a preference over monterey and Ventura?

[syracoj]

I have been so busy I haven't had a chance to update my primary machine so I just use another more updated mac at my disposal when I need to.

[Ιάσονας]

i just downgraded to big sur, the preinstalled py that comes with big sur, is a welcome, im now able to install an app that i couldnt in monterey, even after i typed in terminal python and it installed, kept getting an instal error for the app

in monterey

i notice at idle ram, big sur is using 2gb more then monterey, wonder if that is because of maybe an updated memory compression in monterey,

the red dot in settings alerting me to update was driving me crazy, finally figured out how to get rid of it,

other then that i dont really see a big difference between big sur and monterey

[syracoj]

Andrew,

In the 2024 Crash 2 YT video where it crashes after you smart duplicate the object I do not see any CER report from you that looks like it came from that crash. Are you able to reliably reproduce that crash? And if so, can you crash again but this time fill out the CER or shoot me the CER number? 

I tried to repro with the implied reproduction steps (model out base shape, use insert edge loop through multi-cut, bevel, then cut some more using multi-cut, then smart duplicate) but I have not been able to crash.

[PhilRadford]

I'm having these exact same issues. Duplicating simple objects with crash after crash all day long and I need to be using 2024 . 

[PhilRadford]

I tried switching to 2024.1 yesterday and I still have the crashes due to simple operations such as duplicating a sphere in a populated scene. Im on about 15 crashes today and I have been working for 3 hours. I am also screen recording a maya 2024 workflow and having to restart the recordings over and over. 2023 was much more stable for me. Has something significant changed in the architecture that might be putting some kind of load on the graphics card that 2023 did not? Attached a screen recording of combining a simple piece of geo and a crash with zero log.
Here in this scene I am just creating a low res collision object to use in bifrost graph, I hit combine to combine two very simple geo's and crash. I also get the same with duplicating geometry, simple stuff. What 'are' the recommended drivers for 2024.1 ? and how do they differ from 2023 drivers? 

[PhilRadford]

Update is that I installed recommended drivers only to have a crash after 3 minutes of working, this time moving a vert.
At least I got a crash log:

//=====================================================
Maya Crash Report
//=====================================================

Exception code: C0000005: ACCESS_VIOLATION - illegal write at address 0x9F849488
Fault address: 9F849488 in C:\Program Files\Autodesk\Maya2024\bin\OGSDevices.dll
0002:00007488 Logical offset (see .map file for location)

Call stack:
End of stack

//crash log file name = C:\Users\Phil\AppData\Local\Temp\MayaCrashLog230629.1055.log
//version = 24.1.0.4816
//cut = 04/19/2023, 202304191415
//current scene = unDisclosed
//command history (most recent last):
//====================================================
//last tool: nurbsSelect
//====================================================
//panel with focus: modelPanel3
//visible panels:
// modelPanel3 outlinerPanel1
//====================================================
//Memory usage:
// 240672.703 Mb Free Memory
// 275547.246 Mb Free Swap
// 4678.758 Mb Current

//====================================================

[brentmc]

Hi Phil,

What happens if you disable GPU Override in Windows > General > Evaluation Toolkit > Modes?

In 2024 Maya uses GPU readback to do more evaluation on the GPU so if disabling GPU Override helps it might give us some clues as to where these crashes are coming from.

Thanks.

[PhilRadford]

Hi, ok I immediately tried this as im desperately trying to get this to work but unfortunately I'm still having crashes, this time just deleting history on an object.
Here is the crash log:

//=====================================================
Maya Crash Report
//=====================================================

Exception code: C0000005: ACCESS_VIOLATION - illegal write at address 0x9E299488
Fault address: 9E299488 in C:\Program Files\Autodesk\Maya2024\bin\OGSDevices.dll
0002:00007488 Logical offset (see .map file for location)

Call stack:
End of stack

//crash log file name = C:\Users\Phil\AppData\Local\Temp\MayaCrashLog230629.1126.log
//version = 24.1.0.4816
//cut = 04/19/2023, 202304191415
//current scene = unDisclosed
//command history (most recent last):
//====================================================
//last tool: Move
//====================================================
//panel with focus: modelPanel3
//visible panels:
// modelPanel3 outlinerPanel1
//====================================================
//Memory usage:
// 240880.348 Mb Free Memory
// 275504.199 Mb Free Swap
// 4209.598 Mb Current

//====================================================

[PhilRadford]

Some information. 
HP z840
24 core -48 thread
1080ti
256gb ram
Windows 10pro 64
Writing to an ssd drive.
-Bifrost graph seems to be the only stable part of Maya right now, anything that is purely Bifrost graph is fine, anything Maya side - geo translation, history changes/deletion, geo duplication, creating live surfaces and then switching live off, quad drawing poly surfaces -deleting history, many cases and causes which result in crashes either instant with no log or with log.
Things I have tried include deleting imported geos with any complexity to them, removing imported shaders, optimizing scene including unknown nodes, exporting and importing to new scenes. Updating drivers and GPU override -off.

[andrewsilke]

Disabling the GPU override hasn't helped here.  I have noticed this is specific to modelling and in certain scenes.  Duplicating objects etc.  When I'm animating and doing other tasks, it seems ok. 

I have sent my scene, and I've been told AD has been unable to reproduce the crashing.  Seems like it's affecting a lot of people. 

I'm also on GTX 1080s 1070s btw.  

[PhilRadford]

I just switched from parallel to DG, oddly seems calmer right now. Will update

[PhilRadford]

Still fine after working for an hour and I have been doing everything that was causing crashes before. Not saying it will fix it for everyone but so far for me changing from parallel to DG is doing the trick.