We are using build 878 and this issue seems to be the same as it was with 872.
I know there were some "memory leak" issues resolved in previous versions, but as this is limited to processing of large corridors I suppose we'll have to wait for CONNECT.
I know there were some "memory leak" issues resolved in previous versions, but as this is limited to processing of large corridors I suppose we'll have to wait for CONNECT.