Bug 210629 - Krusader doesn't warn against viewing huge files
Summary: Krusader doesn't warn against viewing huge files
Status: RESOLVED FIXED
Alias: None
Product: krusader
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Shie Erlich
URL:
Keywords:
: 246424 (view as bug list)
Depends on:
Blocks:
 
Reported: 2009-10-15 05:27 UTC by Michał Z. Gołębiowski
Modified: 2011-03-05 13:09 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Michał Z. Gołębiowski 2009-10-15 05:27:25 UTC 
Version:           2.0.0-1ubuntu2 (using KDE 4.3.2)
Compiler:          gcc/g++ 4.4.1-1ubuntu2 
OS:                Linux
Installed from:    Ubuntu Packages

I tried to view a 700 MB video file (by pressing F3) and Krusader didn't warn me that it is going to open a huge file. I have 4 GB RAM and no swap, but with 1 GB RAM & 1 GB swap (which I had on my old laptop) I suppose it would severely slow down an entire OS.

See also https://bugs.launchpad.net/ubuntu/+source/krusader/+bug/451862.
Comment 1 Michał Z. Gołębiowski 2010-05-05 21:24:44 UTC 
I think it should be marked as confirmed; I checked it on:
1) Ubuntu Hardy on my old ASUS notebook
2) Ubuntu Karmic on my new DELL notebook
3) Ubuntu Lucid on my new DELL notebook
and I was able to reproduce the bug in all these cases.

Besides, it is very easily reproducible.

Today I accidentally pressed the F3 button after clicking a 4 GB file and OS killed many other useful apps before killing Krusader - the cause of this mess. I think this bug deserves much wider attention than what it has experienced so far.
Comment 2 Marcin Gryszkalis 2011-03-05 12:22:22 UTC 
Krusader 2.3.0 viewer has Lister mode that can handle files of any size, it's called if viewed file is larger than specified size.
Comment 3 Marcin Gryszkalis 2011-03-05 13:09:39 UTC 
*** Bug 246424 has been marked as a duplicate of this bug. ***