DynamoDS / DynamoRevit

Dynamo Libraries for Revit
https://dynamobim.org
336 stars 187 forks source link

Dynamo is unusable, run starts and just hangs #1118

Open teocomi opened 8 years ago

teocomi commented 8 years ago

Dynamo version

1.0.0 (also tried with the latest daily build)

Revit version

2016 (works fine in the sandbox and in 2015)

Operating system

Windows 7

What did you do?

Any opereation that would require Dynamo to run, makes it hang undefinitely, even just creating a point. This happens both in Automatic and manual Mode, also, part of the UI doesn't get stuck as I can pan around the canvas and modify the components, but in the lower left conrner it keeps showing "Run started..." and nothing happens.

Solutions tested:

I also checked the Log and nothing unusual shows there. This is really confusing as Dynamo used to work fine, but all of a sudden it stopped. See attached gif.

160713_dynamo_bug

kronz commented 8 years ago

@teocomi do you have an active operation in Revit? Is this intermittant or all the time? Are there addins in Revit 2016 that you do not have in Revit 2015? One other diagnostic to try: Dynamo 1.1 (latest release) has a Notifications Display that surfaces additional errors or conflicts that may not be apparent for other issues.

2016-08-02_2241

teocomi commented 8 years ago

Hey @kronz, thanks for looking into this. It first happened while working on a project but now even in blank new ones. Dynamo 1.1 shows no conflict, as I metioned earlier, I even tried removing all Revit and Dynamo addins and it made no change. It seems like Dynamo got corrupted but even uninstalling&reinstalling doesn't fix it.

I'll try to debug it from VS, but let met me know if anything else pops in your mind.

dynamo_bug

teocomi commented 8 years ago

@kronz Dynamo seems to be hanging on this loop in the Heartbeat class (reporting has been turned off):

image

The RequestRun() function in HomeWorkspaceModel is not even hit:

image

kronz commented 8 years ago

@sharadkjaiswal can you take a look at this? @jnealb can you try and reproduce with instrumentation turned off?

teocomi commented 8 years ago

Additional note, I went for lunch and after ~1h the function returned the result:

image

mjkkirschner commented 8 years ago

@teocomi if you disconnect from the internet do you notice any difference? Just curious.

sharadkjaiswal commented 8 years ago

Heartbeat class is not changed, I am not sure why it gets into a race condition. @teocomi Can you please see if there is any other thread blocking the execution. Does DynamoSandbox.exe work fine for you?

teocomi commented 8 years ago

@mjkkirschner unfortunately no difference if disconnected or connected to other network. @sharadkjaiswal both the sandbox and 2015 version work fine

sharadkjaiswal commented 8 years ago

I can't reproduce this issue locally. Can you please let us know the list of Revit add-ins getting loaded on startup?

sharadkjaiswal commented 8 years ago

If you can build Dynamo and run that can you please try disabling heartbeat by commenting out the instance creation at https://github.com/DynamoDS/Dynamo/blob/master/src/DynamoCore/Logging/DynamoAnalyticsClient.cs#L36, just want to verify if Heartbeat is the real culprit.

teocomi commented 8 years ago

@sharadkjaiswal I understand it's a very singular issue as I cannot reproduce it as well on other machines. I'm also quite positive it's not due to other addins as I've tried:

Commenting out the Heartbeat also doesn't fixt it, I'll do some more debugging and let you know if I find something.

sharadkjaiswal commented 8 years ago

@teocomi, I appreciate your analysis, please keep us posted when you identify the core issue.

MKrzynowek commented 6 years ago

Not much of a help, but same thing here. Win 8.1 Revit 2019 Dynamo 2.0.1.5056 Very simple definitions calculate unworkable amounts of time ( 15min +) Please help.

theoryshaw commented 5 years ago

same.

Win 10 Revit 2019 Dynamo 2.0.2.6826

MKrzynowek commented 5 years ago

Hi All, upgrading to Revit 2019.1 worked for me.

theoryshaw commented 5 years ago

Thanks @MKrzynowek upgrading to 2019.2 worked for me as well. Thx.