Skip to content
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

Open
munin2k opened this issue Jun 5, 2024 · 4 comments
Open

Indexer Crashed - AppImage 1.4.0 #776

munin2k opened this issue Jun 5, 2024 · 4 comments

Comments

@munin2k
Copy link

munin2k commented Jun 5, 2024

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:

 08:09 - Indexer Crashed - The indexer worker process crashed. If this problem persists please contact us at .
 08:09 - Indexer Crashed - The indexer worker process crashed. If this problem persists please contact us at .

The following appears in the kernel messages:

[Wed Jun  5 08:09:04 2024] indexer[7887]: segfault at 0 ip 0000000000000000 sp 00007fffd4fb6518 error 14 in indexer[5f67b0499000+1b000] likely on CPU 5 (core 2, socket 0)
[Wed Jun  5 08:09:04 2024] Code: Unable to access opcode bytes at 0xffffffffffffffd6.
[Wed Jun  5 08:09:04 2024] indexer[7892]: segfault at 0 ip 0000000000000000 sp 00007ffc93998578 error 14 in indexer[625f6e756000+1b000] likely on CPU 1 (core 0, socket 0)
[Wed Jun  5 08:09:04 2024] Code: Unable to access opcode bytes at 0xffffffffffffffd6.

Best regards
munin2k

@johnny-mayo
Copy link

johnny-mayo commented Jun 21, 2024

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
[ 1408.070674] traps: indexer[5040] general protection fault ip:7fff3adc3cd0 sp:7fff3ad8f8b8 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
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?

@johnny-mayo
Copy link

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 .
12:41 PM - Indexer Crashed - The indexer worker process crashed. If this problem persists please contact us at .

@johnny-mayo
Copy link

johnny-mayo commented Jun 21, 2024

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 can create a new repository.
I can open my existing project.

I compiled from master, not from the most recent development branch.
I've tweaked the build script for my purposes.
WARNING - this will delete the Gittyup directory
WARNING - I don't know what I'm doing
NOTE - I am not using "git checkout deps", but the result works fine
WARNING - did I mention that I don't know what I'm doing?

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
sudo apt install cmake
sudo apt install libgit2-dev
sudo apt install cmark
sudo apt install git
sudo apt install libssh2-1-dev
sudo apt install openssl
sudo apt install qtbase5-dev qtchooser qt5-qmake qtbase5-dev-tools
sudo apt install qttools5-dev
sudo apt install ninja-build

rm -rf Gittyup
git clone https://github.com/Murmele/Gittyup.git
cd Gittyup

git checkout master
git pull origin master

git submodule init
git submodule update

cd dep/openssl/openssl/
./config -fPIC
make

cd ../../..
mkdir -vp build/release
cd build/release
cmake -G Ninja -DCMAKE_BUILD_TYPE=Release ../..
ninja

===============================================

This was after I tried the following (which failed):

flatpak uninstall com.github.Murmele.Gittyup
rm -rf ~/.var/app/com.github.Murmele.Gittyup
rm -rf ~/.local/share/flatpak/Gittyup
rm -rf ~/.local/share/Gittyup
rm -rf ~/.config/gittyup.github.com
rm -rf ~/python/step4

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.

@johnny-mayo
Copy link

johnny-mayo commented Jul 12, 2024

I've figured out why indexer is segfaulting, and other stuff. I am looking for feedback.
Please see: #789

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants