[BUG] #537
Labels
Comments
|
My apologies missed the title during submission, rare for me to do that. sorry about that. |
|
Hey, thx for the bug report. It's hard to tell what's going wrong here. Can you launch FSearch with following command?
This will give you much more debug output and it might give us a better idea about what's going wrong. |
|
so this is the last few lines right after my search parameter is entered. (fsearch:180119): fsearch-query-tree-DEBUG: 19:59:14.072: * output: [ascii_icase:'fileisearchedfor':CP] |
|
Does the app also freeze when you index other folders? |
|
Also can you debug FSearch with gdb like so:
|
|
for me the gdb debugger doesnt want to launch fsearch, how ever it does launch through terminal the regular way (typing in fsearch) the debugger simply states there are no symbols found in fsearch Once this comes up there is no output from it at all. which is unusual ive placed plenty of programs through gdb and never had a problem with it reading it. running the latest version of gdb that is available as well I checked that I wasn't out of date. |
|
Finally figured out the problem with gdb. this is the last line where it outputs at crashed. there How ever here is the rest of the stuff before that: |
|
The relevant part of the output I need is from those commands:
Does the app crash or freeze? |
|
just freezes, sorry bad word to use for this situation. here is info threads: |
|
Thx, that was helpful. The application seems to be freezing while performing Is there any output in the system log when you get FSearch to freeze? You can monitor the system log with:
|
|
output was large, i put it in paste bin, that paste will burn its self after it is read so if you open it and its not there let me know. Im interested to find out exactly what is going on as all my drives seem to be working, not exactly sure why it would be failing, no errors are reported in the smart data etc. but that also doesnt mean there isnt a problem. ive had drives that have died with out warning before, so if it is a drive id definitely like to figure out that issue. Bear in mine too that there are only 3 drives that live on this machine. The other 3 are are a usb dock, could it be waiting and freezing because of drive sleep on those drives? also it doesnt seem to spin them up so not sure if thats related or not. As the area of failing drives or spin up of the drives is not my expertise. |
|
Thx, I got the debug output. There's nothing in there indicating any issues with filesystem issues. So let's try a few other things:
|
|
ok so disabled the icons, that seemed to fix the issue, however to help you out further to fix it these are the other things: database is 101,996,761 files the freeze happened when i got close to the scroll bar limit going down. since ive disabled the icons the issue is completely gone. all files are indexed and searchable so far. Config is here: |
In order to render the icon the app needs to access the file system (to determine the file type and load the proper icon). And I think the problem here is, that due to the large database the amount of requests to the file system, while quickly scrolling, just becomes too much for the system. Does the issue also happen when the database isn't updating at the same time?
That's quite a lot of files. I've never tested FSearch with that many files, so there might be a few other issues, which I've not noticed yet.
What happens when you hit the And btw. thx for providing all those debug information and helping me to understand and solve the issue! |
|
so i turned on the icons to test the end key, still freezes on the end key the issue is still present regardless of the database being updated or whether it is refreshing. as long as the icons are on, it freezes. no worries at all. one of the few software i truly think should be by default installed on any linux system is fsearch. its the closest thing to everything, and even though i dont use windows any more, that was one of the software that was holding me to windows, i have a really large amount of data. One of the things i do want to know is that is fsearch capable of network storage searching? is there a way to set this up for me to enable remote addresses the drive ? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Freezes on every search, every time it sits for a while.
Errors that are available in the terminal if run this way:
(fsearch:43580): fsearch-database-WARNING **: 16:59:40.205: [db_scan] walk error: 1
but that error occurs long before a freeze and the program is still operational until scroll down or left for a long period. The software has no visible memory leaks.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
for it not to freeze..
Desktop
VC Keymap: au
X11 Layout: au
X11 Model: pc105
The text was updated successfully, but these errors were encountered: