-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Segfaults while using the search functionality #598
Comments
That must be a very rare edge case in our search algorithm then. Can you please see if you can find the |
I did some quick greps on the core dump for some keywords contained by the index and I got positive matches so I'm unable to send you a core dump due to risk of exposing what some of the people that I work with would consider sensitive information. I realize that this will be less efficient but perhaps we could figure it out another way. This is the backtrace that I got by running Sourcetrail through gdb when it crashed:
I do have to admit though it does look weird that the segfault occurred in isupper. |
Thank you, that looks useful! Probably an access at the wrong index, i will look into it. |
Should be fixed with 2018.2.105 The We will release a new beta build next week, I will let you know when it's available. |
New beta release is available. Can you please test if this issue is still present? |
I'll reindex and give it a go. This might take a while though. |
@egraether I am not able to reproduce the issue using the beta version. Seems like this was it. |
Thank you! |
Platform version: Linux (archlinux latest)
Sourcetrail version: 2018.2.77
Description of the problem: Sourcetrail crashes with a segfault when I'm using the search box to input search queries. This seems to happen only on one of the indexes that I use and only when the query starts with the letter 't'. I did notice that it's less likely for it to crash if I type my query slower, for example, if I type
tv
in the search box then the program will in 99% of the cases instantly crash however If I typet
wait 2-3 seconds followed byv
then sometimes it will survive.Steps to reproduce the problem: Type queries in the search box.
Unfortunately I cannot share the index for debugging purposes but I hope the description along with the log bellow can give you some clues as to where the problem might lie.
The text was updated successfully, but these errors were encountered: