Referencer 1.0.2 consumes all memory on 64-bit machine?

[John Spray]

Referencer create an (empty) file, and then hangs (no screen redraw)
while gradually consuming all RAM in the machine. (I've got 4G) IIRC,
it also uses 100% CPU during this hang.

Could you try attaching gdb to the hung process? To do this, start gdb,
then type "attach [pid]" where [pid] is the process ID of the hung
process ("ps -A | grep referencer"), and then type "bt".

I've only got 1.0.2 - do you know if the 1.0.3 version fixes this?
If
so, I'll forward that comment on to the Debian package maintainer,
which
might get the 1.0.3 package out faster :)

As far as I recall nothing in the file IO changed 1.0.2->1.0.3, so I
doubt it makes a difference.

Cheers,
John

[John Spray]

Hmm... does this help? I'm not sure if '??' means that the stack trace
is corrupt...

Looks like it was built without debugging symbols (that's what the ??s
mean). Any chance you could do a "apt-get build-dep referencer" and
then download and build the tarball from the website? That should build
with debugging symbols by default and be easier to mess around with
generally.

Also, does it make any difference if you try saving a library with no
document in? You can kid referencer into letting you save an empty
library by adding a document and then removing it. What about a
different document, such as one created with "Add empty reference"?

Regards,
John