<!--- Please read this! Before opening a new issue, make sure to search for keywords in the issues filtered by the "regression" or "type::bug" label: - https://gitlab.com/gitlab-org/gitlab/issues?label_name%5B%5D=regression - https://gitlab.com/gitlab-org/gitlab/issues?label_name%5B%5D=type::bug and verify the issue you're about to submit isn't a duplicate. ---> ### Summary <!--Summarize the bug encountered concisely.--> When a commit has a very large description (larger than 1MB and several thousand lines), leading the commit history page may timeout. The timeout was identified to be tied to a the [Banzai pipeline](https://docs.gitlab.com/development/gitlab_flavored_markdown/banzai_pipeline_and_parsing/) which renders markdown in the backend before showing the commits summary in the commit history page. ``` json.exception.class Rack::Timeout::RequestTimeoutException json.exception.message Request ran for longer than 60000ms ``` As a workaround, we used the newly added timeframe(https://gitlab.com/gitlab-org/gitlab/-/issues/441117) `committed_before` and `committed_after` to limit the history view but when we select a date wherein the commit with a long description exists, it times out with a 500 error. ### Steps to reproduce <!--Describe how one can reproduce the issue - this is very important. Please use an ordered list.--> * create a large commit with over 1000 lines in the description and larger than 1MB. In particular, use one that has thousands of links that will require markdown rendering. * Select the commit history page and wait for it to timeout with error `500` ### Example Project <!--If possible, please create an example project here on GitLab.com that exhibits the problematic behavior, and link to it here in the bug report. If you are using an older version of GitLab, this will also determine whether the bug is fixed in a more recent version.--> * Internal team members can review a .com case [here](https://gitlab.zendesk.com/agent/tickets/628917) ### What is the current *bug* behavior? <!--Describe what actually happens.--> ### What is the expected *correct* behavior? <!--Describe what you should see instead.--> ### Relevant logs and/or screenshots <!--Paste any relevant logs - please use code blocks (```) to format console output, logs, and code as it's tough to read otherwise.--> * [Kibana logs](https://log.gprd.gitlab.net/app/r/s/S0fO1) * More contex for internal team members in <a href="https://gitlab.com/gitlab-org/gitlab/-/issues/515892#note_2586188139">this issue</a>. * [Sentry stacktrace](https://gitlab.com/gitlab-org/gitlab/-/issues/515892#note_2586390857) ### Output of checks <!--If you are reporting a bug on GitLab.com, uncomment below--> <!--This bug happens on GitLab.com--> <!--and uncomment below if you have /label privileges--> <!--/label ~"reproduced on GitLab.com"--> <!--or follow up with an issue comment of `@gitlab-bot label ~"reproduced on GitLab.com"` if you do not--> #### Results of GitLab environment info <!--Input any relevant GitLab environment information if needed.--> <details> <summary>Expand for output related to GitLab environment info</summary> <pre> (For installations with omnibus-gitlab package run and paste the output of: \\\\\\\`sudo gitlab-rake gitlab:env:info\\\\\\\`) (For installations from source run and paste the output of: \\\\\\\`sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production\\\\\\\`) </pre> </details> #### Results of GitLab application Check <!--Input any relevant GitLab application check information if needed.--> <details> <summary>Expand for output related to the GitLab application check</summary> <pre> (For installations with omnibus-gitlab package run and paste the output of: \\\`sudo gitlab-rake gitlab:check SANITIZE=true\\\`) (For installations from source run and paste the output of: \\\`sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true\\\`) (we will only investigate if the tests are passing) </pre> </details> ### Possible fixes <!--If you can, link to the line of code that might be responsible for the problem.--> The `AutolinkFilter` doesn't respect the limit of [1000 elements](https://gitlab.com/gitlab-org/gitlab/blob/master/lib/banzai/filter.rb#L5-L7). As a result, [this code](https://gitlab.com/gitlab-org/gitlab/-/blob/fa6af6914882e2df235f4c301847808421af325b/lib/banzai/filter/autolink_filter.rb#L74-84) can cause performance issues. ### Patch release information for backports If the bug fix needs to be backported in a [patch release](https://handbook.gitlab.com/handbook/engineering/releases/patch-releases) to a version under [the maintenance policy](https://docs.gitlab.com/policy/maintenance/), please follow the steps on the [patch release runbook for GitLab engineers](https://gitlab.com/gitlab-org/release/docs/-/blob/master/general/patch/engineers.md). Refer to the [internal "Release Information" dashboard](https://dashboards.gitlab.net/d/delivery-release_info/delivery3a-release-information?orgId=1) for information about the next patch release, including the targeted versions, expected release date, and current status. #### High-severity bug remediation To remediate high-severity issues requiring an [internal release](https://handbook.gitlab.com/handbook/engineering/releases/internal-releases/) for single-tenant SaaS instances, refer to the [internal release process for engineers](https://gitlab.com/gitlab-org/release/docs/-/blob/master/general/internal-releases/engineers.md?ref_type=heads). <!--If you don't have /label privileges, follow up with an issue comment of `@gitlab-bot label ~"type::bug"`-->