Revit Crashing When Modifying 2D Grid Extents

[Anonymous]

Hello,

 The challenge my team and I are experiencing revolves around 2D grid extents. We have created a series of enlarged floor plan drawings. When these views are first created, any grid line which passes through them is cropped to an arbitrary offset outside the annotation crop region. Any time we try modify the 2D extents of a grid line in these enlarged plans (1:50) in specifically one of our models, Revit crashes. 

Any thoughts as to why this is happening?

For some background context, we are using BIM360, Revit 2019, and have 12 separate models that are cross-linked into each other. I'm working on a joint venture project where the Revit model was set up by a different architecture firm. The model that keeps crashing is excessive in size - 500MB. Even still, we have 128GB of RAM, 2.5 GHz processor, and a NVIDIA Quadro P4000 video card - none of which max out while this error is occurring. 

The workarounds we are currently utilizing are:

1. If you change the crop extents of the view so that the grid line is no longer within its extents and then extend it so that it is, the grid line will shrink, but by an inapproximate length.

2. If you right-click the grid line, and select "reset to crop region" the grid line extents will move with the crop extents. This, however, does not work as the extents of these enlarged plans are positioned around the area of interest and doesn't have the flexibility to shrink any more. 

3. If you turn off all worksets except the grid line and then modify the 2D extents, the Revit model still crashes. 

Any other suggestions would be greatly appreciated.

[eric.zhang305]

@Anonymous 

I am sorry you are experiencing crashes while working in this project. 

To help find a solution, are you able to reproduce the crash and provide a journal file? Is there a error message that pops up when Revit crashes?

When Revit crashes, does it present a chance to send in a crash report? If it does please enter an email and sent it in, a web page should pop up with report number as well. 

[Anonymous]

Hi Eric,

I've attached the journal file that I believe is associated. There is no error message pops up. The file freezes (for for hours, we've tested) and end up having to force quit. At a loss for possible fixes so any help would be greatly appreciated!

[sasha.crotty]

Hi Daniel,

Please attach the journal file for the associated transaction. Journal files are TXT files (look for Journal.*.txt). The log you included is for a background process that's shouldn't block the main process in way you indicate.

Thanks,

Sasha

[Anonymous]

Hi Sasha,

Sorry. Hope this is the right file.

[eric.zhang305]

@Anonymous 

This journal file was from this morning, did you experience the same behavior? 

I am seeing a lot of collaboration cache issue, I will see about that with my colleagues. 

[Anonymous]

Hi Eric,

Yes, I was experimenting with it some more this morning. Tried using scope boxes but that crops the 3D datum extents not the 2D extents, as desired. There are about 20 uses who work in the models in two offices in two different continents, so lots of collaborators/data.

[eric.zhang305]

@Anonymous 

I have private message you for a model a workflow video. I hope to hear from you soon.

[Anonymous]

Here's that journal file.

[oskyparkin]

Hello,

I would like if you found a solution for this issue. I am experiencing the same issue with Revit crashing (the model freezes) when we are editing the 2D grids, thanks a lot,

Oscar

[rwooten]

My Team is also experiencing this issue. Any updates? 

[emodderman]

I've got a client file with these issues right now. File is only 52mb, so not huge, but the 2D or 3D Level extents cannot be changed at all without Revit running into a tailspin of reprocessing the extents. Currently, there are no scope boxes in use for these extents, but it was an option we were going to try. However it seems from earlier posts that this will not solve the problem.

Did anyone ever get any answers to this?

We're using Revit 2019 on this file, but I've tried Revit 2020 and nothing changed. I will be trying 2021 shortly. 

[rwooten]

For our file, which is pushing 1GB, so much larger, it turns out a number of team members were constraining elements that didn't need to be constrained such as detail items and filled regions that were being copied and pasted through the set, resulting in thousands of constraints. I turned on the show constraints view selected a constrained dimension and deleted all in project. This freed up the grids and levels. I then had to go constrain elements that actually required it. Not sure this solution applies to your situation, but it's what worked for us. Good luck!

[Mikhail.Davtyan]

Did you find a solution?

Have same issue

[plan.control.120]

@Anonymous  

My team and I have the same problem with our projects. Did you find a solution?

We use Revit 2021

This article says that the problem is solved in Revit 2022 but not in other versions of Revit

https://knowledge.autodesk.com/support/revit/troubleshooting/caas/sfdcarticles/sfdcarticles/Slow-performance-when-editing-2D-grids-in-Revit-2019.html

[lvowelsAXEN6]

Modifying the 2D Level Extents continues to be debilitatingly slow and takes 5-10 minutes, even in the latest versions (Revit 2023, Revit 2024). Can this please be addressed?

[akhilanandBF7QN]

Informative 👏.

[seydauzun]

Hi, did you try auditing your file? Also the linked files, you can try to audit linked grid file and load again, and copy monitor again.. Just a suggestion...

[Henry_Marroquin]

I find this is all related to Revit having to check every single element hosted to the level, regardless of the level annotation in the view is set to 2D. I am seeing all the constraints show up (locks) and it's pretty obvious if you set your level annotation to 2D in a view it should not care about what's hosted but here we are using 2023 and this issue crashes every time I try to clean up elevations.