-
-
Notifications
You must be signed in to change notification settings - Fork 113
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Indexer Crashed - AppImage 1.4.0 #776
Comments
I was using the flatpak version of gittyup, when it suddenly stopped showing the gui, as per #783 I've found that the AppImage version of gittyup does work, but when I open any project, even if it is one that I haven't touched in a long time, I'm getting an index error: " 8:36 PM - Indexer Crashed - The indexer worker process crashed. If this problem persists please contact us at ." This problem happens even if I shut down Gittyup, delete .git/gittyup from my project folder, then run Gitttyup and point it at my project folder again. This problem happens even if I open a project I haven't touched in weeks, so I don't think it is in any way something to do with corruption in my current project. I am getting general protection fault kernel messages, different from issue 776: [ 1407.924787] traps: indexer[5038] general protection fault ip:7ffc51f1fcd0 sp:7ffc51eb5fb8 error:0 NOTE: this error only happened today, so I don't think it was happening with the flatpak version of gittyup. Notice, too, that the poster of issue 776 is using the AppImage version of Gittyup. When I ran a "strace ./Gittyup-1.4.0-x86_64.AppImage |& tee gittyup.appimage.strace.log" and did a "grep indexer gittyup.appimage.strace.log", I find the following: stat("/tmp/.mount_GittyuJgFfOi/usr/bin/indexer", {st_mode=S_IFREG|0755, st_size=2505704, ...}) = 0 I DO see /tmp/.mount_..../usr/bin/indexer while Gittyup is running. I see there is a "src/index/indexer.cpp" in the Gittyup source tree. Can someone toss me a clue? What is this indexer? |
I considered some odd problem with AppImage having permission issues when mounting /tmp/mount_...., so I extracted the contents of the Gittyup AppImage, which created a squashfs-root directory tree with Gittyup in it. When I did a cd to squashfs-root and ran ./AppRun, the files were run in place. No /tmp/mount_... was created. The same problem occurs: 12:41 PM - Indexer Crashed - The indexer worker process crashed. If this problem persists please contact us at . |
FIXED...? I was beat and ready to give up, then I thought I would give Gittyup one last shot. I cloned the repository and compiled from source, AND IT WORKED. I get a GUI, and I don't get "Indexer Crashed". Gittyup works perfectly. I compiled from master, not from the most recent development branch. With that said, the following is a script that "works for me" on my up-to-date Debian system. I figure it should work for Ubuntu and similar, based on apt. =============================================== sudo apt install build-essential libgl1-mesa-dev rm -rf Gittyup git checkout master git submodule init cd dep/openssl/openssl/ cd ../../.. =============================================== This was after I tried the following (which failed): flatpak uninstall com.github.Murmele.Gittyup Then, I start the AppImage version of Gittyup and create a new project at ~/python/step4, and I get the same "Indexer Crashed" error. Then I "flatpak install com.github.Murmele.Gittyup" and run the flatpak version, and still, no gui. I really didn't want to reinstall my system from scratch, only for something unknown to change, and have Gittyup stop working again. |
I've figured out why indexer is segfaulting, and other stuff. I am looking for feedback. |
I use Gittyup as AppImage in the current version 1.4.0
Whenever I open a project in Gittyup, the following message appears in the log:
The following appears in the kernel messages:
Best regards
munin2k
The text was updated successfully, but these errors were encountered: