Bug 351362

Summary:	Warn kate user of opening large files
Product:	[Applications] kate	Reporter:	Gregor Mi <codestruct>
Component:	general	Assignee:	KWrite Developers <kwrite-bugs-null>
Status:	RESOLVED DUPLICATE
Severity:	wishlist	CC:	andrew.crouthamel, bizyaev, christoph, karl, oded, waqar.17a
Priority:	NOR
Version:	5.0.0
Target Milestone:	---
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Gregor Mi 2015-08-16 13:05:47 UTC

kate version 15.07.90

According to https://git.reviewboard.kde.org/r/114315/ a warning on opening large binary files should already be implemented.

When I open a 1 GB file or drop it to kate there is no warning and it takes very long until kate becomes responsive again.

Comment 1 Christoph Feck 2015-09-23 18:08:48 UTC

Checking the code from the reviewboard link in comment #0, it looks like it only warns when you are opening using the "File > Open..." dialog, but not when opening through other means (e.g. from the command line).

Comment 2 Gregor Mi 2015-09-28 19:43:06 UTC

Thanks for checking. So I keep the bug open as "consistency issue".

Comment 3 Oded Arbel 2021-01-07 09:56:31 UTC

BTW - this is probably not the correct place to report this, but comparing Kate's behavior with very large files (millions of rows) compared to GNOME's gedit: kate freezes until everything is loaded, while gedit loads incrementally and shows the content, which can be scrolled and selected, while it is loading - and this is a much better behavior. Also, gedit finishes much faster than kate on the same file.

Comment 4 Waqar Ahmed 2021-01-10 08:28:55 UTC

(In reply to Oded Arbel from comment #3)

Yes, that is a limitation we have due to how KTextEditor works. For me, with 8G ram, Kate just crashes on a 300 mb file  ¯\_(ツ)_/¯

See: https://invent.kde.org/frameworks/ktexteditor/-/issues/1

Comment 5 Christoph Cullmann 2023-02-26 22:10:28 UTC

*** Bug 430269 has been marked as a duplicate of this bug. ***

Comment 6 Christoph Cullmann 2023-02-26 22:22:21 UTC

Seems we still have cases that bypass the warning.

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