crash: 1.11.1 randomly crash with SIGBUS when creating an issue #5009

Closed
opened 2025-11-02 06:10:50 -06:00 by GiteaMirror · 5 comments
Owner

Originally created by @dujiulun on GitHub (Mar 6, 2020).

Description

Gitea will randomly crash when I create an issue.

It crashed earlier today; after it was restarted, I created two more issues with no problem. Tonight when I tried to create another, it crashed again.

The log shows SIGBUS, which looks like #2311, which was supposed to be fixed.

Screenshots

Originally created by @dujiulun on GitHub (Mar 6, 2020). <!-- NOTE: If your issue is a security concern, please send an email to security@gitea.io instead of opening a public issue --> <!-- 1. Please speak English, this is the language all maintainers can speak and write. 2. Please ask questions or configuration/deploy problems on our Discord server (https://discord.gg/gitea) or forum (https://discourse.gitea.io). 3. Please take a moment to check that your issue doesn't already exist. 4. Please give all relevant information below for bug reports, because incomplete details will be handled as an invalid report. --> - Gitea version (or commit ref): 1.11.1 - official docker image - Git version: 2.24.1 - Operating system: Docker image (Ubuntu) - Database (use `[x]`): - [ ] PostgreSQL - [x] MySQL - [ ] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [x] No - [ ] Not relevant - Log gist: https://gist.github.com/dujiulun/72436d34e939b082d1fa6a36b305de05 ## Description Gitea will randomly crash when I create an issue. It crashed earlier today; after it was restarted, I created two more issues with no problem. Tonight when I tried to create another, it crashed again. The log shows SIGBUS, which looks like #2311, which was supposed to be fixed. ## Screenshots <!-- **If this issue involves the Web Interface, please include a screenshot** -->
GiteaMirror added the issue/stale label 2025-11-02 06:10:50 -06:00
Author
Owner

@lunny commented on GitHub (Mar 6, 2020):

Looks like a bblot problem used by bleve.

@lunny commented on GitHub (Mar 6, 2020): Looks like a bblot problem used by bleve.
Author
Owner

@guillep2k commented on GitHub (Mar 6, 2020):

My suggestion is to delete the current bleve indexes from the indexer directory so Gitea will rebuild them anew. This procedure must be performed while the instance is shut down. For example:

# cd /var/lib/gitea/indexers # Your directory may be different
# ls -l
total 0
drwx------ 2 git git  67 Oct  9 00:23 issues.bleve
drwxr-xr-x 2 git git 158 Feb  9 23:05 issues.queue
drwx------ 2 git git  67 Oct 14 22:59 repos.bleve
# rm -r issues.bleve repos.bleve
@guillep2k commented on GitHub (Mar 6, 2020): My suggestion is to delete the current bleve indexes from the indexer directory so Gitea will rebuild them anew. **This procedure must be performed while the instance is shut down**. For example: ``` # cd /var/lib/gitea/indexers # Your directory may be different # ls -l total 0 drwx------ 2 git git 67 Oct 9 00:23 issues.bleve drwxr-xr-x 2 git git 158 Feb 9 23:05 issues.queue drwx------ 2 git git 67 Oct 14 22:59 repos.bleve # rm -r issues.bleve repos.bleve ```
Author
Owner

@bagasme commented on GitHub (Mar 7, 2020):

@guillep2k thanks for the workaround

@bagasme commented on GitHub (Mar 7, 2020): @guillep2k thanks for the workaround
Author
Owner

@stale[bot] commented on GitHub (May 6, 2020):

This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.

@stale[bot] commented on GitHub (May 6, 2020): This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.
Author
Owner

@zeripath commented on GitHub (May 6, 2020):

I think this is fixed so I am going to close this. Please reopen if still an issue

@zeripath commented on GitHub (May 6, 2020): I think this is fixed so I am going to close this. Please reopen if still an issue
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#5009