search

DynamoDS / DynamoRevit

Dynamo Libraries for Revit
https://dynamobim.org
328 stars 184 forks source link

Dynamo and Revit Crash when opening script... #2066

Open DanimoSite opened 6 years ago

DanimoSite commented 6 years ago

Dynamo and Revit Crash when opening a script. It is only one script causing the problem. This is one of the most popular scripts we have.

Dynamo version

V 2.0.1

Revit version

2017/2018 latest updates on each

Operating system

Windows 10

What did you do?

Open a script in Dynamo 2.0.1. I had previously upgraded this to 2.0. When i went to open again, caused crashes. I have also tried to open the 1.3.3 version and still causes crash.

What did you expect to see?

The script to open

What did you see instead?

Revit bomb with fatal error.

Note: I have upgraded ALL packages in our 3rd party and internal packages. Script uses a node from the clockwork package, but mostly built-in nodes and our internal package. I have attached the script should you need it. If you need the .dyf files, let me know

Script.zip

Cheers, Dan

smangarole commented 6 years ago

@DanimoSite Thanks for reporting this crash. I tried running both scripts (v2.0 and V1.3) on 2.0.1 and I did not get a crash. I have Clockwork 1.x installed.

  1. Are you using Clockwork for 2.0 by any chance?
  2. Can you send us the stack trace? And relevant screenshots?
  3. What packages are installed on your machine?
  4. Any addins? Example: pyRevit
  5. Can you send the custom nodes (.dyf files) that are used in the scripts?

Thanks, Sid

ricardyn commented 5 years ago

Occurs several similar cases with me. Below follows one of revit journal file end

Jrn.AddInEvent "AddInJournaling" , "WpfWindow(_this,Dynamo).WpfListBox(0,recentListBox).SelectItems(0,Dynamo.UI.Controls.StartPageListItem)" ' 0:< Managed exception occurred: 'C 30-Apr-2019 10:34:12.456; 0:< Collection was modified; enumeration operation may not execute. 'WPF RenderMode at time of exception was: HardwareAccelerated 'C 30-Apr-2019 10:34:12.456; 0:< ExceptionCode=0xe0434352 ExceptionFlags=0x00000001 ExceptionAddress=00007FFEDC21A388 ' 0:< [000037bc]BC: 0,0,1 ' 0:< System (MB) [Available / Total ] [Revit Memory Usage (MB) ] ' 0:< RAM Statistics: 5486 / 16178 1529=InUse 1530=Peak
' 0:< VM Statistics: 134176844 / 134217727 1718=InUse 1719=Peak
' 1:< [000037bc]Revit worker 1 closed cleanly ' 0:< [00004664]QueueMinder stopped 'C 30-Apr-2019 10:34:13.759; 1:< logging finished virtualization services
'C 30-Apr-2019 10:34:13.759; 1:< logging finished worker services
'C 30-Apr-2019 10:34:13.761; 1:< logging erased queues
' 1.289863 1:<<<[000037bc]Terminating Slave Processes ' 0:< ::65:: Delta VM: Avail -6 -> 134176842 MB, Used -7 -> 1710 MB, Peak +0 -> 1719 MB; RAM: Avail +108 -> 5599 MB, Used -1 -> 1526 MB, Peak +1 -> 1530 MB ' 0:< GUI Resource Usage GDI: Avail 9091, Used 909, User: Used 519 'E 30-Apr-2019 10:34:13.805; 0:< Jrn.AddInEvent "AddInJournaling" , "WpfWindow(_this,Dynamo).WpfListBox(0,recentListBox).SelectItems()" ' 0:< unhandledExceptionFilter is executed in a non-main thread (id = 14268, tag = : [was TaskFileExists]).

ricardyn commented 5 years ago

According to the journal file the error seems to occur on some selection node.

In my case the error was only occurring when I tried to open the script in a specific Revit file, since I was able to open it in another empty Revit file.

I deleted the selection nodes from the script and then tried to open again in the Revit file that the problem was occurring and Dynamo opened normally