Indexer crashes #2521

@techknowlogick commented on GitHub (Nov 13, 2018):

Which version of Git are you using?

@techknowlogick commented on GitHub (Nov 13, 2018): Which version of Git are you using?

GiteaMirror commented

@gerroon commented on GitHub (Nov 13, 2018):

git --version
git version 2.19.1

Debian Buster X64

@gerroon commented on GitHub (Nov 13, 2018): git --version git version 2.19.1 Debian Buster X64

GiteaMirror commented

@tYYGH commented on GitHub (Nov 18, 2018):

I have a similar problem: same error message, same status 128. And Gitea is then taking up 44% of my whole RAM!
This is after changing from:

git 2.18.0(-1)
gitea 1.5.1(-1)

to:

git 2.19.1(-1)
gitea 1.5.3(-3)

on Archlinux, with my Ansible configuration applied to app.ini.sample from upstream Gitea.

Please ask for details if you need more.

@tYYGH commented on GitHub (Nov 18, 2018): I have a similar problem: same error message, same status 128. **And Gitea is then taking up 44% of my whole RAM!** This is after changing from: * git 2.18.0(-1) * gitea 1.5.1(-1) to: * git 2.19.1(-1) * gitea 1.5.3(-3) on Archlinux, with [my Ansible configuration](https://yalis.fr/git/yves/home-server/src/branch/master/roles/ihmgit_back/tasks/main.yml#L51) applied to [`app.ini.sample` from upstream Gitea](https://git.archlinux.org/svntogit/community.git/tree/trunk/PKGBUILD?h=packages/gitea#n64). Please ask for details if you need more.

GiteaMirror commented

@xoxys commented on GitHub (Nov 21, 2018):

Same here on RHEL:

updateRepoIndexer: exit status 128 - error: unable to find XXX fatal: git cat-file XXX: bad file

git version 1.8.3.1
gitea 1.5.3

@xoxys commented on GitHub (Nov 21, 2018): Same here on RHEL: `updateRepoIndexer: exit status 128 - error: unable to find XXX fatal: git cat-file XXX: bad file` - git version 1.8.3.1 - gitea 1.5.3

GiteaMirror commented

@markusamshove commented on GitHub (Nov 26, 2018):

Same after updating from 1.5.1 to 1.6.0:

SLES 12
git version 2.12.3
gitea 1.6.0

@markusamshove commented on GitHub (Nov 26, 2018): Same after updating from `1.5.1` to `1.6.0`: * SLES 12 * git version 2.12.3 * gitea 1.6.0

GiteaMirror commented

@laoshaw commented on GitHub (Dec 1, 2018):

Same, using 1.6.0, debian 9 64bit, git 2.17.1

2018/11/30 22:56:10 [.../runtime/asm_amd64.s:1333 goexit()] [E] updateRepoIndexer: exit status 128 - fatal: git cat-file 9d7337a3b028095abbb0ee3dec460544d019d1f6: bad file

@laoshaw commented on GitHub (Dec 1, 2018): Same, using 1.6.0, debian 9 64bit, git 2.17.1 2018/11/30 22:56:10 [.../runtime/asm_amd64.s:1333 goexit()] [E] updateRepoIndexer: exit status 128 - fatal: git cat-file 9d7337a3b028095abbb0ee3dec460544d019d1f6: bad file

GiteaMirror commented

@ll911 commented on GitHub (Dec 18, 2018):

same, using 1.6.1, rhel 7.5 X86_64bit, git 2.14.1

2018/12/17 15:06:09 [...routers/repo/http.go:391 serviceRPC()] [E] fail to serve RPC(upload-pack): exit status 128 - {[102 97 116 97 108 58 32 84 104 101 32 114 101 109 111 116 101 32 101 110 100 32 104 117 110 103 32 117 112 32 117 110 101 120 112 101 99 116 101 100 108 121 10] 0 [0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0] 0}
2018/12/17 17:29:40 [.../runtime/asm_amd64.s:1333 goexit()] [E] updateRepoIndexer: exit status 128 - fatal: git cat-file: could not get object info

@ll911 commented on GitHub (Dec 18, 2018): same, using 1.6.1, rhel 7.5 X86_64bit, git 2.14.1 ``` 2018/12/17 15:06:09 [...routers/repo/http.go:391 serviceRPC()] [E] fail to serve RPC(upload-pack): exit status 128 - {[102 97 116 97 108 58 32 84 104 101 32 114 101 109 111 116 101 32 101 110 100 32 104 117 110 103 32 117 112 32 117 110 101 120 112 101 99 116 101 100 108 121 10] 0 [0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0] 0} 2018/12/17 17:29:40 [.../runtime/asm_amd64.s:1333 goexit()] [E] updateRepoIndexer: exit status 128 - fatal: git cat-file: could not get object info ```

GiteaMirror commented

@markusamshove commented on GitHub (Jan 31, 2019):

This is still present in 1.7 for me

@markusamshove commented on GitHub (Jan 31, 2019): This is still present in 1.7 for me

GiteaMirror commented

@gerroon commented on GitHub (Jan 31, 2019):

The indexer seems to be a bit useless with big repos :(

@gerroon commented on GitHub (Jan 31, 2019): The indexer seems to be a bit useless with big repos :(

GiteaMirror commented

@tYYGH commented on GitHub (Feb 1, 2019):

As things stand, it is also useless with little repos, because you have to disable it to keep it from eating all your RAM :-/

@tYYGH commented on GitHub (Feb 1, 2019): As things stand, it is _also_ useless with little repos, because you have to disable it to keep it from eating all your RAM :-/

GiteaMirror commented

@laoshaw commented on GitHub (Feb 1, 2019):

indexing and searching are essential to code related work, any way to improve this in gitea, as far as I can tell, this is the only obvious weak area at the moment.

@laoshaw commented on GitHub (Feb 1, 2019): indexing and searching are essential to code related work, any way to improve this in gitea, as far as I can tell, this is the only obvious weak area at the moment.

GiteaMirror commented

@lunny commented on GitHub (Feb 7, 2019):

@laoshaw Yes, that needs more work.

@lunny commented on GitHub (Feb 7, 2019): @laoshaw Yes, that needs more work.

GiteaMirror commented

@stale[bot] commented on GitHub (Apr 8, 2019):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

@stale[bot] commented on GitHub (Apr 8, 2019): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

GiteaMirror commented

@tYYGH commented on GitHub (Apr 8, 2019):

Does someone know the current status of this issue?
Also, what are the consequences of switching the indexer off? I wish to understand if this issue is minor or major, as far as I am concerned at least…

@tYYGH commented on GitHub (Apr 8, 2019): Does someone know the current status of this issue? Also, what are the consequences of switching the indexer off? I wish to understand if this issue is minor or major, as far as I am concerned at least…

GiteaMirror commented

@apricote commented on GitHub (Apr 8, 2019):

@tYYGH If you switch the Repo Indexer off, you will not be able to search for code in Gitea anymore.

@apricote commented on GitHub (Apr 8, 2019): @tYYGH If you switch the Repo Indexer off, you will not be able to search for code in Gitea anymore.

GiteaMirror commented

@gerroon commented on GitHub (Apr 8, 2019):

I am wondering about the indexer situation as well. Has there been any improvements?

@gerroon commented on GitHub (Apr 8, 2019): I am wondering about the indexer situation as well. Has there been any improvements?

GiteaMirror commented