From: Andrew Ebling <andyebling@clara.co.uk>
To: gentoo-dev@gentoo.org
Subject: [gentoo-dev] severe gnumeric bug
Date: 19 Jul 2002 13:51:34 +0100 [thread overview]
Message-ID: <1027083094.4569.26.camel@spinel.tao.co.uk> (raw)
Here is how to crash your system using gnumeric 1.0.8
(or bring it close):
(this is the simplest routine that demonstrates the bug).
- open gnumeric
- Edit->Select->All
- Copy
- File->New
- Edit->Paste
The result is long periods of CPU activity, first I watch RAM fill up,
followed by all the swap.
If left to its own devices, gnumeric eventually quits with this message:
---------8<--------------8<-------------------
GLib-ERROR **: could not allocate 16777216 bytes
aborting...
---------8<--------------8<-------------------
Ahem... that is a _lot_ of bytes!
I can see what it is trying to do (allocate enough memory to copy every
(blank) cell of the spreadsheet). However, it really ought to be more
intelligent than to actually try and do that, especially if the cells
are empty.
I don't have time to go through the motions of a formal bug report, I've
briefly searched bugzilla.gnome.org and not come across anything.
Is anyone else able to give this severe bug the attention it deserves?
I discovered it doing everyday work, so it must be affecting quite a lot
of people out there. It also exhibits behaviour that could potentially
endanger the stability of the whole system, especially those that
pre-date the kernel Out Of Memory killer, introduced late in 2.4 iirc.
thanks,
Andy
PS. Please CC me on replies. I'd love to keep up with all the goings
on with this list, but I can't afford the time :-(.
--
The contents of this e-mail and any attachments are confidential and may
be legally privileged. If you have received this e-mail and you are not
a named addressee, please inform us as soon as possible on
+44 118 901 2999 and then delete the e-mail from your system. If you are
not a named addressee you must not copy, use, disclose, distribute,
print or rely on this e-mail. Any views expressed in this e-mail or any
attachments may not necessarily reflect those of Tao's management.
Although we routinely screen for viruses, addressees should scan this
e-mail and any attachments for viruses. Tao makes no representation or
warranty as to the absence of viruses in this e-mail or any attachments.
Please note that for the protection of our business, we may monitor and
read e-mails sent to and from our server(s).
Visit our website at http://tao-group.com/
reply other threads:[~2002-07-19 12:51 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1027083094.4569.26.camel@spinel.tao.co.uk \
--to=andyebling@clara.co.uk \
--cc=gentoo-dev@gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox