Issue 21964 - No warning when file size is too big for OO
Summary: No warning when file size is too big for OO
Status: CONFIRMED
Alias: None
Product: General
Classification: Code
Component: code (show other issues)
Version: OOo 1.1 RC5
Hardware: PC All
: P3 Trivial with 1 vote (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords: oooqa
Depends on:
Blocks:
 
Reported: 2003-10-31 15:11 UTC by magrawal
Modified: 2013-02-07 22:35 UTC (History)
1 user (show)

See Also:
Issue Type: ENHANCEMENT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description magrawal 2003-10-31 15:11:12 UTC
OO should know when a file is too big for it to handle and should not even try 
opening those files. Yesterday I tried opening the date file obtained by 
unzipping the compressed bz2 format router tables at the following site:
http://archive.routeviews.org/oix-route-views/2003.10/
The deflated file size is about 600 MB. When I tried opening this file in Word, 
I immediately got the warning: File size greater than 32 MB, Word cannot open 
the file. I tried opening it in SatrOffice 7, it kept trying to open the file, 
it even expanded the swap space to over 1GB. Even after I left my 1.4GHz P4 
working overnight, SO7 had not opened the file, though it was still trying and 
had not hung up.
Though it is possible that SO7 would eventually have opened the file, I think 
that there should be some kind of test before a file is opened to estimate how 
lon it would take to open the file. If this time is too long (say greater than 2 
minutes), the user should be warned about the estimated time. OO should try to 
open the file only if the user agrees to the time.
Comment 1 utomo99 2003-11-01 03:42:07 UTC
Better solutions if OOo can open the documents Gradually. 
This will solving not only oversized doc like this but also other big
files. 

when we load big files, we can see some page and then OOo can continue
to load the rest and we can working with the ones which already
displayed. 

We better not limiting the file size we can open, but warning is good. 

I think it is framework 
Comment 2 utomo99 2003-11-01 03:44:15 UTC
Reassign issue to owner of selected subcomponent
Comment 3 Olaf Felka 2003-11-03 09:22:52 UTC
Shoukd it be possible to handle such situations?
Comment 4 ace_dent 2008-05-16 02:54:40 UTC
OpenOffice.org Issue Tracker - Feedback Request.

The Issue you raised has the status 'New' pending further action, but has not
been updated within the last 4 years. Please consider re-testing with one of the
latest versions of OOo, as the problem(s) may have already been addressed.
Either use the recent stable version: http://download.openoffice.org/index.html
or consider trying the new OOo 3 BETA (still in testing):
http://download.openoffice.org/3.0beta/
 
Please report back the outcome so this Issue may be Closed or Progressed as
necessary - otherwise it may be Resolved as Invalid in the future. You may also
wish to search for (and note) any duplicates of this Issue that may have
advanced further by checking the Issue Tracker:
http://www.openoffice.org/issues/query.cgi
 
Many thanks,
Andrew
 
Cleaning-up and Closing old Issues as part of:
~ The Grand Bug Squash, pre v3 ~
http://marketing.openoffice.org/3.0/announcementbeta.html
Comment 5 bettina.haberer 2010-05-21 14:59:19 UTC
To grep the issues easier via "requirements" I put the issues currently lying on
my owner to the owner "requirements".