Gitea freezes while merging a PR #9524

Closed
opened 2025-11-02 08:41:46 -06:00 by GiteaMirror · 4 comments
Owner

Originally created by @ghost on GitHub (Sep 6, 2022).

Description

We use Gitea 1.17.1 which should have fixed PRs stuck on "Merge conflict checking is in progress. Try again in few moments." · Issue #17204 · go-gitea/gitea . However, the bug is still there. UI sometimes hangs even dozens of minutes with "Merge conflict checking is in progress. Try again in few moments." This really slows down the development process (we merge 10 PRs every day) and causes a lot of frustration among the developers.

Gitea Version

1.17.1

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

No response

Screenshots

No response

Git Version

No response

Operating System

No response

How are you running Gitea?

We run it on command-line.

Database

No response

Originally created by @ghost on GitHub (Sep 6, 2022). ### Description We use Gitea 1.17.1 which should have fixed [PRs stuck on "Merge conflict checking is in progress. Try again in few moments." · Issue #17204 · go-gitea/gitea](https://github.com/go-gitea/gitea/issues/17204) . However, the bug is still there. UI sometimes hangs even dozens of minutes with "Merge conflict checking is in progress. Try again in few moments." This really slows down the development process (we merge 10 PRs every day) and causes a lot of frustration among the developers. ### Gitea Version 1.17.1 ### Can you reproduce the bug on the Gitea demo site? No ### Log Gist _No response_ ### Screenshots _No response_ ### Git Version _No response_ ### Operating System _No response_ ### How are you running Gitea? We run it on command-line. ### Database _No response_
GiteaMirror added the issue/needs-feedback label 2025-11-02 08:41:46 -06:00
Author
Owner

@nazario29 commented on GitHub (Sep 9, 2022):

I can replicate the same issue with gitea 1.17.2 and let me add more detail:

  1. First of all I can only see this problem happening when we have a big chunk of changes, in branches with 3 or 4 file changes I see no problem.
  2. I open the Pull Request via gitea UI and immediately we see memory from the client's PC raising nonstop until it hits 4 or 5 GB memory and then it throws a browser message about "Out of memory"
@nazario29 commented on GitHub (Sep 9, 2022): I can replicate the same issue with gitea 1.17.2 and let me add more detail: 1. First of all I can only see this problem happening when we have a big chunk of changes, in branches with 3 or 4 file changes I see no problem. 1. I open the Pull Request via gitea UI and immediately we see memory from the client's PC raising nonstop until it hits 4 or 5 GB memory and then it throws a browser message about "Out of memory"
Author
Owner

@CypherpunkSamurai commented on GitHub (Sep 10, 2022):

Hello Mr. @nazario29,

Is it possible to enable logging on the instance? It would really help the issue if you can replicate the bug and collect logs. Thank you :)

@CypherpunkSamurai commented on GitHub (Sep 10, 2022): Hello Mr. @nazario29, Is it possible to enable logging on the instance? It would really help the issue if you can replicate the bug and collect logs. Thank you :)
Author
Owner

@zeripath commented on GitHub (Oct 10, 2022):

Without logs we have no hope of being able to debug this.

@zeripath commented on GitHub (Oct 10, 2022): Without logs we have no hope of being able to debug this.
Author
Owner

@zeripath commented on GitHub (Oct 17, 2022):

I think it would also be helpful to review your app.ini too.

@zeripath commented on GitHub (Oct 17, 2022): I think it would also be helpful to review your app.ini too.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#9524