Strange issue here, but i havent been in Revit 2023 all that much this year. Typically i have been in 2022 or 2024. Working on a job in 2023.1.5 now, and running some Dynamo Graphs.
Dynamo is crashing NOT during the RUNNING of the Graph, but if i:
- Go to File > Open (sometimes)
- Go to File > Open Recent Graph (almost always)
- Click the X on the Graph to try to close it.
When it happens, i just get a Crash Report.
SOMETIMES im getting this weird SENDDMP message, too.
The issue is, if i cant close a graph without crashing Dynamo (which takes Revit with it, obviously), there isnt any point running the graphs. LOL.
Anyone else ever run in to this?
First I am seeing this - can you send me a Dynamo log and Revit journal? If you can reproduce it easily in a screen recording that would help too.
Feel free to DM or email if thatâs easier.
1 Like
Logs.7z (9.4 KB)
Journals.7z (496.0 KB)
Journals and Dynamo Logs attached. The latest one from today crashed differently because i disabled the Workspace References tool, and that crash was less destructive since it didnt take Revit with it.
But any of the ones from last night will show the crash. The logs just say Uunhandled Exception, at least where i looked. I can get a screen capture of it, but it doesnt show anything good.
Ill make a recording here in a few.
Update: So i pivoted to my Laptop, thinking the Desktop has some issue that needs to be solved for⌠And my Laptop does the exact same thing.
Which makes me think something in our â23023 configâ isnt happy. Could be a package version we have loaded, could be an extension, could be the base install (i hope not). But its not specific to this machine, which is interesting.
1 Like
That the workspace references being disabled causes a different crash is a good data point.
I smell an add-in conflict.
Can you try the Jacob Small Special â˘ď¸ (As so declared in Monocle by John) and disable ALL your Revit add-ins and see if that clears it.
Iâm having dinner at the moment, but Iâll have a look at the journals when done.
1 Like
Revit addins, or Dynamo Packages? I can do both.
Ill start with Revit addins.
Revit add-ins to start with. Dynamo add-ins wouldnât crash Revit. Well unless the add-in was touching Revit in a bad way⌠if it repeats disable the Dynamo customizations second.
Dynamo is super easy to disable though - just rename the appdata path for your build (i.e. rename the 2.16 folder to ânopenopenowaynohownevernopeâ), and the folder should rebuild clean on the fly.
It took an extra day to get back to testing this, because i/we use a lot of our addins all the time, but⌠Now i am running Revit 2023 with 95% of the addins shut off. The only one that is running is the Autodesk Collaborate app, which i need because the model in question is on ACC. LOL.
Still crashing, at File Open in Dynamo.
ZERO third party addins running.
1 Like
Interesting. It seems like not having the graph saved is contributing, potentially. If i save the graph, and THEN âXâ out of Dynamo, it⌠doesnt crash.
Havent tried the File Open aspect yet, or the Open Recent. Will try that tomorrow.
1 Like
Are the graphs on the local system?
They are stored where all of our graphs are stored, for all versions of Dynamo.
Thatâs a hardwired Storage appliance on the LAN, so nothing strange about file access or availability.
But not local on the local hard drive, as we would never save anything important on the local hard drive.
Assuming these arenât a âone offâ, but used for many projects, why not treat them like other code that is reused by many users? For a example you save the source code for an add-in on the network (or a repo), but you run the add-in off your C drive. Why not do the same with your Dynamo graphs?
Any chance I can get the journal from the session without add-ins?
Because Dynamo Graphs are more like Excel docs, in how they get used, compared to Static programs. They are on shared storage because we all use them, sometimes lightly modify them, and always want to be using the latest versions. The graph itself isnt an application that never changes or is updated.
But for testing purposes, i moved all graphs locally, and went in to DynamoSettings.xml and wiped out the Recent Files, so its no longer looking at the UNC path of the Network Drive for anything.
I will use the same processes this morning to see if it reproduces the crash, and post the Journals. Still running with no Revit addins at all, for diagnostics.
1 Like
LocalRunLog.7z (3.7 KB)
journal.0026.txt.7z (60.3 KB)
Dynamo Logs and Revit Journal attached, from this morning.
Its a SHORT session, since i literally just went:
- Open Revit 2023
- Open the model
- Open the Graph
- Make one node change
- Run the graph
- Go to open another graph
- Crashed
1 Like
UghâŚ
â 0:< API_ERROR { : Assembly version conflict in some references in DynamoPlayerExtension assembly
'Addinâs module Newtonsoft.Json of version 11.0.0.0 conflicts with same preloaded module of version 13.0.0.0 }
Iâm calling it: the windows and any attempt at a common operating environment was a mistake. We should all go back to DOS.
So should i disable Dynamo Player? I dont use it, so that wouldnt hurt me at all.
Nope - there is a newtonsoft conflict somewhere iwth a proceeding add-in. Dynamo and Player both use 13 (or should) but somewhere along the line something is installing 11 which is a conflict, but not necessarily a problem or the root cause here.
The actual crash isnât recorded in the journal (as you likely know) just a generic dialog box with only one button that I am not sure you even saw.
Thats wild, because ACC is the only Addin running.
LOL
I guess i misspoke, and Insights is also running. I can kill both of those (but then i cant use ACC, lol).
Yeah - something is loading it but I canât tell what. Might be that the stantec tool isnât catching something due to an odd setup or ânot really being an add-inâ in the traditional sense (i.e. IFC Exporter).
