SlickEdit Community
SlickEdit Product Discussion => SlickEdit® => Topic started by: rowbearto on July 27, 2020, 06:52:59 PM
-
With 24.0.2/hotfix16 I loaded a very large binary file, size 776M Bytes.
In my buffer I'm currently at byte offset 0x307f01b0.
I wanted to go to a different byte offset so I clicked on the "Search" menu in the menu bar with the intent to "Go to offset". SE then freezes a long time. While it is frozen I see "Searching(...)..." in the status bar.
-
Is it reproducable?
If so, maybe you can zip up the file and post it to support.
This type of thing can be caused by a timer callback kicking in and doing some smart feature. We've addressed every case we've found but every now and then a new one pops up. Its usually just a matter of avoiding doing the work under a large file circumstance.
-
Unfortunately when I tried it again about 20 minutes later it didn't happen :(
-
It's possible it depends on the specific cursor location.
-
Yes if I go to the offset 0x307f01b0 using "gui-seek" as I mentioned in my first post it reproduces!
I tar xzipped it and put it on support, look for:
largebin.tar.xz
on support. Go to offset 0x307f01b0 and click "Search".
-
A menu item is fetching the current word. We will need to put a performance fix in cur_word(). The crux of the problem is that there is an insanely long line which was being used as a way to break out of a search. That just isn't good enough for the length of this line.
-
Added hot fix. Also fixed for v25 beta 2.