No Code Attached Yet
avatar blackkn8
blackkn8
25 Jan 2025

Steps to reproduce the issue

I uploaded to a web server (hetzner Level 9) a Joomla Installation (5.2.0 Stable) and after installation I make an "regular" update to Version 5.2.3.
After updating, it was not possible anymore to add new users. Each time I got the error:
Fatal error: Allowed memory size of 402653184 bytes exhausted (tried to allocate 20480 bytes) in /usr/www/users/xxx/xxx.de/libraries/src/HTML/Helpers/Select.php on line 387

Fatal error: Allowed memory size of 402653184 bytes exhausted (tried to allocate 65536 bytes) in /usr/www/users/xxx/xxx.de/libraries/vendor/symfony/error-handler/Exception/FlattenException.php on line 391

Fatal error: Allowed memory size of 402653184 bytes exhausted (tried to allocate 65536 bytes) in Unknown on line 0

Warning: Unknown: Cannot call session save handler in a recursive manner in Unknown on line 0

See screen
https://ncloud.kkimmerle.eu/index.php/s/qfCPJromz6NsWoD

Expected result

Regular form to add users.

Actual result

Got php error page see attached

System information (as much as possible)

Hetzner Webser (Level 9)
etting Value
PHP Built On Linux www48.your-server.de 6.1.0-28-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.119-1 (2024-11-22) x86_64
Database Type mysql
Database Version 10.11.6-MariaDB-hetzner1
Database Collation utf8mb4_general_ci
Database Connection Collation utf8mb4_general_ci
Database Connection Encryption None
Database Server Supports Connection Encryption Yes
PHP Version 8.1.31
Web Server Apache

Setting Value
Upload Max Filesize 300M
Post Max Size 300M
Memory Limit 384M
Open basedir None
Display Errors On
Short Open Tags On
File Uploads On
Output Buffering Off
Session Save Path /usr/home/kmsxwi/.tmp
Session Auto Start 0
XML Enabled Yes
Zlib Enabled Yes
Native ZIP Enabled Yes
Disabled Functions None
Fileinfo Available Yes
Multibyte String (mbstring) Enabled Yes
GD Available Yes
iconv Available Yes
intl Available Yes
Maximum Input Variables 1000
max_execution_time 90

Additional comments

I tested this (3 times) with a "fresh" installation and in each try I got this problem.

My first intention, was to check the memory limit but with 384M it should be enough. And it was interesting, by "decrasing" the Problem stayed, but the value of required memory shrinks, too. And increasing to more than 384M is atm not possible because then I need a plan upgrade.... ;-)

I also checked the rights and tried it also with the maximum (777) nothing helps, and I also checked the permission to all folders, and get no suspected details.

But to be honest, I'm hosting a similar Joomla instance on a self-hosted hetzner server with php8.1 and only memory limit of 128M and there it works. (if no solution will be found, I must move it to the self-hosted environment. But this is not what I'm looking for.

So I'm pretty sure that there could be a problem in some code compatibilities. But that it is out of my experiences.

An update to the 5.3.0-alpha3 Version did not help.
And I was also changing the PHP Version to 8.2, 8.3 and 8.4

Votes

# of Users Experiencing Issue
0/1
Average Importance Score
1.00

avatar blackkn8 blackkn8 - open - 25 Jan 2025
avatar blackkn8 blackkn8 - change - 25 Jan 2025
Labels Removed: ?
avatar joomla-cms-bot joomla-cms-bot - change - 25 Jan 2025
Labels Added: No Code Attached Yet
avatar joomla-cms-bot joomla-cms-bot - labeled - 25 Jan 2025
avatar chmst
chmst - comment - 26 Jan 2025

Cannot replicate the issue. Please try to reinstall core files.

avatar richard67
richard67 - comment - 26 Jan 2025

@blackkn8 Do you have the possibility to use an own php.ini or .user.ini file so you can modify some php.ini values (within the limits of your hosting)? If yes: Could you check if it helps to increase the max_input_vars from 1000 to e.g. 2000 or 3000?

avatar brianteeman
brianteeman - comment - 26 Jan 2025

the problem is most likely to be the session save path or session save method

avatar blackkn8
blackkn8 - comment - 26 Jan 2025

@chmst I tried this, no changes. And sadly also with 3 full new installations. May be it is a bad condition of server settings.

@richard67 that I will try, good idea.

@brianteeman and what should I supposed to do?

I will try later to start with a installation of Version 5.2.3 instead of 5.2 may be this will make any differences, too.

Many thanks to all of you who will have an idea, to fix this.


This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/44779.

avatar Hackwar
Hackwar - comment - 26 Jan 2025

It is kinda strange that it is reporting that it is trying to allocate exactly (2^11)*10 and 2^16 bytes. These rund numbers are hinting at some other sort of issue here.

avatar Hackwar
Hackwar - comment - 26 Jan 2025

How did you install Joomla? Are you using a package from joomla.org or a quickinstaller from Hetzner? Do you have any additional PHP extensions installed?

avatar brianteeman
brianteeman - comment - 26 Jan 2025

google the error. It is caused by php session configuration and is nothing caused by Joomla

avatar blackkn8
blackkn8 - comment - 27 Jan 2025

Many thanks for all your advice, but I was able to narrow down the error. When I used a "newer" installation version (5.2.3 Full Stable), I was able to add new users. However, after adding additional new fields, I encountered the error again. Voilà, I could identify my problem.

Here's what I did:

  1. Added a new Field Group named VTES (the name isn't important).

  2. Added a new Field named VEKN (the name isn't relevant, but the type is).
    Type of field: Integer
    Required: Yes (not necessarily required, but done in my test because we need its value).

  3. Set the following properties for the field:
    First: 1000000
    Last: 9999999
    Step Increment: 1
    (Yes I need numbers with 7 digits!)

  4. Added this field to the Group VTES and published it!

After saving this field, if I tried to create a new user, the error occurred again.

My solution is now to use the "text" type instead of integer. Although I can live with this workaround, it should ideally be possible to create an integer field with these settings.

The problem is, that VEKN is a User ID or an external ID number, we need to identify users.


This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/44779.

avatar blackkn8
blackkn8 - comment - 27 Jan 2025

you can see it here... => https://ncloud.kkimmerle.eu/index.php/s/7EDAEHDz6PFHesg . (The error will be the same)
From my point of view this can be closed. (Because I got a work around)
But also from my point of view this should be a bug.... . or?


This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/44779.

avatar alikon alikon - change - 27 Jan 2025
Status New Closed
Closed_Date 0000-00-00 00:00:00 2025-01-27 08:22:25
Closed_By alikon
avatar alikon alikon - close - 27 Jan 2025
avatar alikon
alikon - comment - 27 Jan 2025

this has been already reported #42579

and there is a pr #43697 also + workaround

Add a Comment

Login with GitHub to post a comment