Bug 298904 - kde become no-response when kwrite opens a file that contains only three specific bytes
Summary: kde become no-response when kwrite opens a file that contains only three spec...
Status: RESOLVED DUPLICATE of bug 272579
Alias: None
Product: kate
Classification: Applications
Component: kwrite (show other bugs)
Version: unspecified
Platform: Fedora RPMs Linux
: NOR critical
Target Milestone: ---
Assignee: KWrite Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-04-27 12:49 UTC by raysoft
Modified: 2012-04-27 17:47 UTC (History)
0 users

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


Attachments
this file(3 bytes) contains EF BB BF (3 bytes, application/octet-stream)
2012-04-27 13:03 UTC, raysoft
Details

Note You need to log in before you can comment on or make changes to this bug.
Description raysoft 2012-04-27 12:49:13 UTC
CPU utility is very high and it costs lots of RAM then kde become no-response when kwrite opens a file that contains only 3 bytes: EF BB BF.
However, there is no problem if I use gedit or vim to open this file.

Reproducible: Always

Steps to Reproduce:
1.create a new file
2.use any hex-editor to input these three bytes(in hex): EF BB BF
3.use kwrite to open this file
Actual Results:  
high CPU utility and it costs more and more memory and then kde becomes no-response

Expected Results:  
kwrite should open it very fast

My OS is Fedora 15 x86_64 and I use KDE 4.6.5
Comment 1 raysoft 2012-04-27 13:03:38 UTC
Created attachment 70702 [details]
this file(3 bytes) contains EF BB BF

Computer will become no-response when kwrite opens this file because it costs too much RAM
Comment 2 Dominik Haumann 2012-04-27 17:47:14 UTC
Was fixed for KDE 4.7, please update. I will add your file as test case, though.

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