The hang has been fixed upstream. It was (and the as-values
thing mostly was) a matter of taking an extremely long time,
not a hang per se.
Morten
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
The as values problems are fixed upstream.
Morten
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
On Thu, Nov 04, 2010 at 11:21:07 -0400, Morten Welinder wrote:
The as values problems are fixed upstream.
Specifically:
http://git.gnome.org/browse/gnumeric/commit/?id=bca4b6ccadbad690f17d28ad710ff67bed3e6f14
plus
I am unable to reproduce the ods save issue. It does use a lot of cpu
for a short
while, but then finishes as expected. Your stack trace suggests that it did
finish.
I am unclear on how to reproduce the the BadAlloc crash. Could you please spell
out the steps in detail? I.e., what is selected
I am unable to reproduce the ods save issue. It does use a lot of cpu
for a short
while, but then finishes as expected. Your stack trace suggests that it did
finish.
I had to press Ctrl-C and then used to the command bt to obtain the
trace. I then promptly exited gdb and killed gnumeric
Ok, got it. Fix will land upstream shortly. The problem is that
the dragging of the little square (as opposed to dragging of the
data) is creating a crazy-tall tooltip that gtk+ cannot handle.
You can use copy+paste instead.
Note: you are better off using HYPOT over IMABS+COMPLEX.
The latter
On Thu, Nov 04, 2010 at 16:26:27 -0400, Morten Welinder wrote:
Ok, got it. Fix will land upstream shortly.
Landed as
http://git.gnome.org/browse/gnumeric/commit/?id=f40daf97c2c369dce9572b93feaf896ceb47a30c
--
First they ignore you.
Then they laugh at you.
Then they fight you.
Then you win.
I am unable to reproduce the ods save issue. It does use a lot of cpu
for a short
while, but then finishes as expected. Your stack trace suggests that it did
finish.
Ok, so these are the steps that cause my cpu usage to soar to 100% and
stay there until I kill the process when saving to an
8 matches
Mail list logo
