|
I encountered a runaway memory leak in PgS 4.1.6.21 that I'm missing some
steps to reproduce. I'm posting to the list in the hopes that someone else
has seen similar behavior and maybe some correlations can be made to find out
how to reproduce it.
What I was doing:
I'd opened a multi-chapter document and had done some very modest text editing
in the main article of a chapter. I then created a table (the table tool) and
had been busy adding columns, entering text and generally tweaking it.
What went wrong:
I decided that I had one column too many so I switched to the reshape tool and
clicked into the undesired (right-most) column. Having done that I clicked
the button for turning two columns into one.
It took a few seconds to run me out of memory and swap. Fortunately the kernel
killed PgS so the only thing I lost was the last few edits (save often, save
more often).
However, doing this with a clean document works. Moreover, I reopened the
document I'd been working on and repeated the steps to delete the column and
it worked flawlessly.
The only thing I can even think of at this point is that it may have taken PgS
a noticeable amount of time to remove the column. Because of this I think I
clicked twice on the remove column button. I have periodic, noticeable,
delays (its what I get for loading a new background image from across the
network every few minutes) and if I clicked twice that might have messed PgS
up (though IMO a runaway like that should not happen).
I just tried reproducing that with no success so I might be barking up the
wrong tree.
Tim Doty
|
