After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 72969 - crash after importing a very big file (gnumeric Crash at 217.141.18.213)
crash after importing a very big file (gnumeric Crash at 217.141.18.213)
Status: RESOLVED FIXED
Product: Gnumeric
Classification: Applications
Component: General
unspecified
Other other
: Normal normal
: ---
Assigned To: Jody Goldberg
Jody Goldberg
Depends on:
Blocks:
 
 
Reported: 2002-02-28 11:44 UTC by cristiano_mariani
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description cristiano_mariani 2002-02-28 11:44:48 UTC
Package: gnumeric
Version: 0.67
Severity: 

>Synopsis: crash after importing a very big file
>Class: sw-bug
System: HP Vl400 redhat 7.2, gnumeric opened via ReflectionX (on NT workstation), importing 372069 line files

>Description:
Importing a BIG file (text) gnumeric chrash
the file is a squid.chache log file



>How-To-Repeat:
i was trying to import a very big file ( 372069 lines ), i started Gnimeric, after this open file menu, import an then selected the file.
using the option text file.

after this (i know 372069 are more than 65536 lines :) ) the Linux was thinking and , 3, 2, 1 ..... Boom!
crashed :)

i think may be all.


best regards, Cristiano

Whish list:

if 372069 lines are too much, adding a control for thisk kind of  error may be a good idea, but best is a utility for split the file in more than 1 page or enabling more then 65536 lines.
ciao




------- Bug moved to this database by unknown@bugzilla.gnome.org 2002-02-28 06:44 -------

The original reporter (cristiano_mariani@cemarsrl.it) of this bug does not have an account here.
Reassigning to the exporter, unknown@bugzilla.gnome.org.
Reassigning to the default owner of the component, jody@gnome.org.

Comment 1 Morten Welinder 2002-02-28 20:28:32 UTC
I would guess this has been fixed.  Please try 1.0.4.  If that does
not help, reopen.