Power InRoads V8i (SS4)- System Out of Memory Error Received when modeling corridors

Hello,

When modeling corridors within Power InRoads V8i (SS4) the following dialog box pops up with a memory error. The current solution is to exit out of the program, re-open, and then run the corridor model again. This error message typically rears it's ugly head after modeling corridors within Power InRoads V8i (SS4). It's not the specific amount of time that you're using Power InRoads V8i (SS4), or the number of times your modeling or re-modeling any particular corridor. It also doesn't matter if the corridor is simple or complex. Appreciate any assistance with this issue.

 

Thanks,

Larry

Parents
  • These will often pop up for no reason that can be discovered by us mere mortals. Sometimes, we just deal with it best we can. Projects which were started in the infamous version 845 seem to be more prone to such mysteries.

    Very large corridor files can cause problems. While it may not be obvious until you do a detailed investigation, large corridors which consume 2gb of ram are a prime suspect.  That does not mean that the DGN file is 2GB.  It might only be a couple hundred MB.  But with the overhead of OpenRoads/Microstation plus processing overhead, you can consume 2GB of ram pretty easy of the corridor is more than 2 miles long and or is very complex. 

    There also seem to be some processes which leak memory, meaning that a process starts and does its thing but never returns the memory for use by other processes.  if this is the case, you will notice that the memory used by PowerInRoads will continue to increase in task manager, sometimes even when it is just sitting still.  Once it hits 2GB you are done.

    What can you do? If the corridor is large, split it into multiple dgn files of shorter length. Otherwise, if you can isolate any particular workflow or tool which triggers the crash, not much you can do other than soldier on.

    Robert Garrett
    Senior Consultant

    www.envisioncad.com

Reply
  • These will often pop up for no reason that can be discovered by us mere mortals. Sometimes, we just deal with it best we can. Projects which were started in the infamous version 845 seem to be more prone to such mysteries.

    Very large corridor files can cause problems. While it may not be obvious until you do a detailed investigation, large corridors which consume 2gb of ram are a prime suspect.  That does not mean that the DGN file is 2GB.  It might only be a couple hundred MB.  But with the overhead of OpenRoads/Microstation plus processing overhead, you can consume 2GB of ram pretty easy of the corridor is more than 2 miles long and or is very complex. 

    There also seem to be some processes which leak memory, meaning that a process starts and does its thing but never returns the memory for use by other processes.  if this is the case, you will notice that the memory used by PowerInRoads will continue to increase in task manager, sometimes even when it is just sitting still.  Once it hits 2GB you are done.

    What can you do? If the corridor is large, split it into multiple dgn files of shorter length. Otherwise, if you can isolate any particular workflow or tool which triggers the crash, not much you can do other than soldier on.

    Robert Garrett
    Senior Consultant

    www.envisioncad.com

Children
No Data