FIXED: Hang on ctrl+home after ctrl+End

[Qihe Pan]

After performing a Ctrl+End, using Ctrl+Home causes the APP to hang or maybe just a very long time to response.
I'm editing a file with 300MB and 5738840 lines.

[pjj]

I can see this can happen with a highlighter other then "Text file" (I switched on a random highlighter for 80 MB logfile and my editor chocked a bit). So ad hoc solution is to switch off highlighter.

[Rickard Johansson]

There is an option to "Open large files as plain text". It's turned off by default, but should perhaps be turned on.

It seems most editors have a limit and turns off the highlighter when the file size gets too large...

[Qihe Pan]

There is an option to "Open large files as plain text". It's turned off by default, but should perhaps be turned on.

It seems most editors have a limit and turns off the highlighter when the file size gets too large...

It still hangs even if I turn on this option.

[Rickard Johansson]

I think I'm going to need an example file. I've tried with files larger than 500 MB without any issues.

[Qihe Pan]

I think I'm going to need an example file. I've tried with files larger than 500 MB without any issues.

I have enclosed a file that can reproduce the issue. By the way, I'm using the portable version of the app on Windows 10. Here are the steps I took:

Pressed ctrl + Home
Pressed ctrl + End
Pressed ctrl + Home

[pjj]

No hanging for me, Ctrl-Home and Ctrl-End work instantaneously. Highlighter: text file, Windows 7.

Counting items takes a little time (but not too much, 3 sec top), the same replacing items. "Find next" works right off the bat. Scrolling up and down is smooth.

I have 24 GB not-so-quick RAM (800 MHz) and Intel Core i5 3,4 GHz.

[Rickard Johansson]

I can't reproduce it either. Do you use an highlighter, or display the file as plain text?

[Rickard Johansson]

Created a new simple Log file highlighter.

log.png (10.08 KiB) Viewed 394 times

Made some optimizations and Ctrl+End should only take a few seconds to scroll to the end of file (even if there are 6.851.016 lines ).

Note! No highlighter (plain text) is still faster though...

[Qihe Pan]

The 'Open large files as plain text(MB)' option is enabled. I'm using window 10.

[Qihe Pan]

The 'Open large files as plain text(MB)' option is enabled. I'm using window 10.

All other options are using default values and I'm using the 16.26(64-bit) portable version.

[Qihe Pan]

The 'Open large files as plain text(MB)' option is enabled. I'm using window 10.

All other options are using default values and I'm using the 16.26(64-bit) portable version.

After open the file with RJ TextEd, I did the following operations. The APP was hanging on the 2nd time of CTRL+Home.
Pressed ctrl + Home, not hanging
Pressed ctrl + End, not hanging
Pressed ctrl + Home, hanging

[Qihe Pan]

I have 8GB RAM and Intel(R) Core(TM) i5-6200U CPU @ 2.30GHz 2.40 GHz.

[pjj]

On my another, "toy" machine with Windows 10 (Pentium 1.1 GHz, though probably overclocked a tad, and 4 Gb RAM), I was able to hang RJ TextEd (16.20, installed) only while counting substrings. Simple loading given file was quite quick, and changing highlighter to "Log" took like 10 sec. Even with this highlighter on, Ctrl-Home/Ctrl-End were acting instantaneously.

[Rickard Johansson]

Fixed in next release (v16.21 beta 3). It only happens when the document map is visible