On Fri, Jun 03, 2011 at 04:09:46PM +0100, Thomas Oldbury wrote: > This might explain my problem with PCB+GL.... maybe it's just a general > problem with PCB? I have noticed that PCB can eat up about 3 GB after a > few hours of routing. >
The bug appears to have been introduced by the following commit, which had some pretty far-reaching changes: commit 2ce35292b9e96da38cb56878005aba20891689eb Author: Peter Clifton <pc...@cam.ac.uk> Date: Sat Apr 30 15:20:39 2011 +0100 Convert board objects to GLists of g_slice allocated memory This enables pointers for these objects to be immutable during their lifetime, which is a _huge_ benefit for some operations. Having otherwise was becoming VERY tiresome, and was a perenial source of bugs tripping up novice and experts of the codebase alike. Due to the risks associated with modifying the structure being iterated over, this patch makes the relevant *_LOOP macros iterate over a shallow copy of the underlying GList. This is slight overkill for many cases, but until we have identified which do not modify the data-structures it is wise to keep as we are. -- Andrew Poelstra Email: asp11 at sfu.ca OR apoelstra at wpsoftware.net Web: http://www.wpsoftware.net/andrew/ _______________________________________________ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user