AC19 - Memory Leak with Snap Guides and/or Snap Points

[Anonymous]

There might be a memory leak when there are multiple instances of AC19 open and if in one (or maybe more) has a snap guide or snap point active and that instance is put in the back ground.

At least on my machine, which has 6gigs, it will slowly chew up memory until I've seen instances that are 4.8 gigs in size.

If I click on them and bring them to the foreground and kill the active snap guide or point that will release the memory.

[Laszlo Nagy]

Hi mbeam,

I will forward this issue to the Graphisoft developers. I am sure they will be interested in finding out if this is indeed an issue and if so, what causes it so they can fix it.
Could you by any chance provide step-by-step instructions on how to create this situation in ARCHICAD so that this memory leaking issues starts happening?
Maybe if you could also create a PLA file and upload it to Dropbox or similar site so others can look at the file and test it?

It would also be helpful and important to know the operating system you are working on as it may be happening only on specific operating systems.
(You could fill out your Signature in your Forum Profile.)

[Anonymous]

Updated my sig. The OS is Win7.

Happens to me regardless of what files I use so if it's not my computer this shouldn't require any specific pla to work.

Just fully activate a snap guide or point and I think when it starts to try to calculate snap guides off those snaps that's what's ticking off the memory.

But just bring something else to the fore ground without dismissing the snaps and after a while it should start eating memory until that instance is brought to focus and the snaps dismissed.

It has no problem returning the memory to the system but I've had more than a few open and if they're sitting in the back ground undisturbed by me for days because I'm not working on them they have the time to grow so big they've made the computer stagger and then crash.

Thank dog for auto save.

[Katalin Borszeki]

Hi, we have entered this problem as a defect! The workaround for the meantime is to save and close the .pln in case you do not expect to work on it for an extended period.
Thanks much for the report, kata