Don't reset the extension lists in system requirements [#3588490]

Problem/Motivation

SystemRequirementsHooks::checkRequirements() resets the module + theme extension lists.

Because it's called on every admin page due to update requirements, this means that cache_bootstrap is invalidated every request when you're navigating around admin pages.

We can add a way to get the uncached extension list without invalidating the cached one.

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

Introduced terminology

API changes

Data model changes

Release notes snippet

Comment	File	Size	Author
#5	3588490-nr-bot_ekuvd8y3.txt	1.15 KB	needs-review-queue-bot

Issue fork drupal-3588490

Show commands

Start within a Git clone of the project using the version control instructions.

Add & fetch this issue fork’s repository

Or, if you do not have SSH keys set up on git.drupalcode.org:

Add & fetch this issue fork’s repository

3588490-dont-reset-the changes, plain diff MR !15668
Check out this branch for the first time

Check out existing branch, if you already have it locally

About issue forks

Comments

Comment #1

5 May 2026 at 14:54

catch created an issue. See original summary.

Comment #2

catch

he/him

English

commented 5 May 2026 at 14:59

Status:

Active

» Needs review

Comment #3

5 May 2026 at 15:01

catch opened merge request !15668

Comment #4

catch

he/him

English

commented 5 May 2026 at 15:25

Issue summary:

View changes

Comment #5

needs-review-queue-bot commented 5 May 2026 at 15:25

Status:

Needs review

» Needs work

Status	File	Size
new	3588490-nr-bot_ekuvd8y3.txt	1.15 KB

The Needs Review Queue Bot tested this issue. It fails the Drupal core commit checks. Therefore, this issue status is now "Needs work".

This does not mean that the patch necessarily needs to be re-rolled or the MR rebased. Read the Issue Summary, the issue tags and the latest discussion here to determine what needs to be done.

Consult the Drupal Contributor Guide to find step-by-step guides for working with issues.

Comment #6

andypost

he/him

Russian

commented 5 May 2026 at 16:04

Priority:

Normal

» Major

how come this happened?! sounds major at least

Comment #7

andypost

he/him

Russian

commented 5 May 2026 at 16:06

Issue tags:

+Needs change record

Comment #8

berdir

German

Switzerland

commented 5 May 2026 at 20:54

Nice find, I commented on why this IMHO fails so hard right now. There's also #3336621: Running hook_requirements() on all admin pages is very expensive to help with the "runs on every/many admin pages" and improve that.

Comment #9

catch

he/him

English

commented 5 May 2026 at 21:41

@andypost I think this goes back to Drupal 7 or earlier and has been ported around.

Comment #10

catch

he/him

English

commented 5 May 2026 at 21:49

Drupal 7 system_requirements() calls system_rebuild_module_data() - which both built the system data but also wrote it, so that confirms 'ported from at least Drupal 7' for why it's like this.

https://api.drupal.org/api/drupal/modules%21system%21system.install/func...
https://api.drupal.org/api/drupal/modules%21system%21system.module/funct...