On Sat, 2011-06-04 at 10:51 -0700, Andrew Poelstra wrote:
Another leak can be seen when zooming in and out. Typing
Zz on the board takes another 12Mb.
It is only a leak if repeated cycles continue to cause this extra memory
to be allocated.
It is quite possible that hitting different
On Mon, 6 Jun 2011 02:10:10 -0700
Andrew Poelstra as...@sfu.ca wrote:
There are two leaks I fixed:
1. ENDALL_LOOP did not free memory. Now it does.
2. If you return early from a list using the macro.h macros,
list memory is not freed. I added an END_LOOP_EARLY macro
to
On Mon, Jun 06, 2011 at 11:00:51AM -0700, Colin D Bennett wrote:
I do: C++. Automatic destruction is your friend.
ducks and runs :-)
Maybe for memory -- but for more complex resources this
doesn't work in C++ because there is no way to signal
errors from a destructor.
In fact, if a
On Mon, 6 Jun 2011 11:29:57 -0700
Andrew Poelstra as...@sfu.ca wrote:
On Mon, Jun 06, 2011 at 11:00:51AM -0700, Colin D Bennett wrote:
I do: C++. Automatic destruction is your friend.
ducks and runs :-)
Maybe for memory -- but for more complex resources this
doesn't work in C++
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
I think I've got it. The following patch (also posted on
Launchpad) fixes the bug on my system. I am posting it here
for review and testing.
There are two leaks I fixed:
1. ENDALL_LOOP did not free memory. Now it does.
2. If you return early from a list using the macro.h macros,
list
On Fri, Jun 03, 2011 at 11:55:51PM -0700, Andrew Poelstra wrote:
The problem happens in the loop in rats.c, lines 766-784.
There are two functions called, GetNetMemory and GetConnectionMemory.
The first builds up an array of Nets, allocating them in blocks
of 100 (4800 bytes) as needed.
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.
On 3 June 2011 14:41, Kai-Martin Knaak [1]kn...@iqo.uni-hannover.de
wrote:
Andrew Poelstra wrote:
Use gdb to
On Fri, Jun 03, 2011 at 03:41:41PM +0200, Kai-Martin Knaak wrote:
This seems to be a memory leak problem. I noted, that memory usage goes way up
on rats optimization until it hits the ceiling (memory and swap used 100%).
See the system log I attached to the lauchpad bug report.
Andrew Poelstra wrote:
The problem happens in the loop in rats.c, lines 766-784.
That was quick!
I hope, this issue is resolved soon.
---)kaimartin(---
--
Kai-Martin Knaak
Email: k...@familieknaak.de
Öffentlicher PGP-Schlüssel:
http://pool.sks-keyservers.net:11371/pks/lookup?search=0x6C0B9F53
Hi.
A fresh clone from git of PCB just failed on me with memory error. While
I did some manual routing of a fairly large layout (~1700 components) the
application died after several minutes. There was an error message on the
command line:
***MEMORY-ERROR***: pcb-head[21193]: GSlice: failed to
On Thu, Jun 02, 2011 at 11:45:01PM +0200, Kai-Martin Knaak wrote:
Hi.
A fresh clone from git of PCB just failed on me with memory error. While
I did some manual routing of a fairly large layout (~1700 components) the
application died after several minutes. There was an error message on the
12 matches
Mail list logo
