Problem/Motivation

Visiting the batch ops page exhausts system memory on Drupal 11

Steps to reproduce

Just install on Drupal 11 and visit the page. Doesn't matter if you have a module that implements batches or not. The problem exists in both circumstances.

Issue fork codit_batch_operations-3482565

Command icon Show commands

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

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

About issue forks

Comments

cdesautels created an issue. See original summary.

swirt’s picture

swirt
he/him
Primary language English
commented

Thank you for reporting this. I will take a look into it soon.

swirt’s picture

swirt
he/him
Primary language English
commented

Confirmed that I am seeing this on SimplyTest.me with a default install of Drupal 11.4

Here is the error
Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 262144 bytes) in /var/lib/tugboat/stm/web/modules/contrib/codit_batch_operations/src/BatchOperations.php on line 221

swirt’s picture

swirt
he/him
Primary language English
commented
Assigned: Unassigned » swirt

In testing this, I found that now that #3482564: Config page throws fatal error on D11 is fixed and you can set a default user, the error goes away on D11. So that is the immediate workaround.

The bug still exists in the background though, so I am going to work on this.

swirt opened merge request !27

  • swirt committed 9dbc681b on 1.0.x 
    #3482565 Resolve error for when default user is not set.
swirt’s picture

swirt
he/him
Primary language English
commented
Status: Active » Fixed

This was due to it trying to load user 0 when no default user had been specified. It now uses user 1 if no default user is specified in the settings.

swirt’s picture

swirt
he/him
Primary language English
commented
Status: Fixed » Closed (fixed)

Released as 1.0.5