Bug 246424

Summary:	krusader tries to load WHOLE big file into memory on F3
Product:	[Applications] krusader	Reporter:	freeman3
Component:	general	Assignee:	Shie Erlich <manson>
Status:	RESOLVED DUPLICATE
Severity:	major	CC:	gregap, jan_lepper, mg
Priority:	NOR
Version First Reported In:	0.65
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:	2.3.0-beta1
Sentry Crash Report:

Description freeman3 2010-08-01 14:47:22 UTC

Version:           0.65 (using KDE 4.4.4) 
OS:                Linux

when I accidentally press F3 on a big file that krusader doesn't recognize, it tries to load whole file into the memory and open it. I happened multiple times to me, when I open for ex 4 GB file, it effectively kills the system. I have opened only 130MB file, but Krusader takes now 500MB of memory even after I have closed the file viewer.

Reproducible: Always

Steps to Reproduce:
try to open any big file and see what happens. I have tries it on avi file now. Btw it should play the avi file not open it in text viewer.

Actual Results:  
System is unusable because lack of memory

Expected Results:  
Display warning or open only a part of that file

OS: Linux (x86_64) release 2.6.34-12-desktop
Compiler: gcc

Comment 1 Gregor Petrin 2010-12-20 15:29:48 UTC

This has been fixed in the latest SVN version of Krusader, opening a file larger than X (this is configurable, seems to be set to 10MB by default) will open it in Lister which doesn't load files into memory completely but only views a small segment of the file instead.

Comment 2 Marcin Gryszkalis 2011-03-05 13:08:02 UTC


*** This bug has been marked as a duplicate of bug 178793 ***

Comment 3 Marcin Gryszkalis 2011-03-05 13:09:39 UTC


*** This bug has been marked as a duplicate of bug 210629 ***