Allowed memory size of<> bytes exhausted (MrdBallTree.php#450)

[GHBLoos]

Which version of recognize are you using?

8.2.0

Enabled Modes

Face recognition

TensorFlow mode

Normal mode

Downstream App

Memories App

Which Nextcloud version do you have installed?

30.0.4

Which Operating system do you have installed?

Linux 4.18.0-513.5.1.el8_9.x86_64 x86_64

Which database are you running Nextcloud on?

mysql/MariaDB 10.3.39

Which Docker container are you using to run Nextcloud? (if applicable)

No response

How much RAM does your server have?

7.5GB

What processor Architecture does your CPU have?

AMD EPYC Processor (with IBPB) (4 threads)

Describe the Bug

Error in log file (I always get them two at the time). At night I receive them (probably the cron job) and also when uploading (multiple) images.

[PHP] Fout: Allowed memory size of 1073741824 bytes exhausted (tried to allocate 655360 bytes) at /var/www/cloud.DOMAIN.TLD/html/apps/recognize/lib/Clustering/MrdBallTree.php#450
	from ? by -- at 2 apr 2025, 20:49:43

I have these errors for a long time.

My PHP info:

Version: 8.2.12
Memory limit: 1 GB
Max time: 3600
Max. upload size: 1 GB
Frequentie OPcache validation: 2

Extensions: Core, date, libxml, openssl, pcre, zlib, filter, hash, json, random, Reflection, SPL, session, standard, cgi-fcgi, bcmath, bz2, calendar, ctype, curl, dom, mbstring, fileinfo, ftp, gd, gettext, gmp, iconv, intl, exif, mysqlnd, PDO, Phar, posix, shmop, SimpleXML, sockets, sodium, sqlite3, sysvmsg, sysvsem, sysvshm, tokenizer, xml, xmlwriter, xsl, mysqli, pdo_mysql, pdo_sqlite, xmlreader, zip, apcu, igbinary, imagick, msgpack, redis, Zend OPcache

Extra info, probably not relates:

Also after manually downloading the models, this status keeps returning

Expected Behavior

I don't expect an error. I have no clue if this means the image is not analysed

To Reproduce

1. Uploading images (I think it's always with multiple images)
2. cron job at night

Debug log

No response

[marcelklehr]

Hello @GHBLoos
It appears this is an issue with the clustering batch size and the PHP memory limit. Could you try increasing the PHP memory limit to 2GB perhaps? If this is not an option you can try running the occ recognize:cluster-faces command with the --batch parameter set to a number lower than 10000 (which is the default for the cron job), e.g. try occ recognize:cluster-faces -b 5000.

[GHBLoos]

Could you try increasing the PHP memory limit to 2GB perhaps?
Unfortunately that did not work. I will try the --batch parameter soon

[GHBLoos]

@02:15

occ recognize:cluster-faces -b 5000
[root@<srv> html]# sudo -u apache php occ recognize:cluster-faces -b 5000
Clustering face detections for user <>
ClusterDebug: Retrieving face detections for user <>
ClusterDebug: Not enough face detections found
Clustering face detections for user <>
ClusterDebug: Retrieving face detections for user <>
...
Clustering face detections for user <>
ClusterDebug: Retrieving face detections for user <>
ClusterDebug: Found 2087 fresh detections. Adding 1250 old detections and 1663 sampled detections from already existing clusters. Calculating clusters on 5000 detections.
ClusterDebug: Clustering complete. Total num of clustered detections: 1245
Clustering face detections for user <>
ClusterDebug: Retrieving face detections for user <>
ClusterDebug: Found 500 fresh detections. Adding 1250 old detections and 3310 sampled detections from already existing clusters. Calculating clusters on 5060 detections.
ClusterDebug: Clustering complete. Total num of clustered detections: 87

@03:08

PHP Fatal error:  Allowed memory size of 3221225472 bytes exhausted (tried to allocate 655360 bytes) in /var/www/<CLOUDDOMAIN>/html/apps/recognize/lib/Clustering/MrdBallTree.php on line 448

[GHBLoos]

Can I manually change the cron job? Can you give a hint where to find the cron job file for Recognize?

[marcelklehr]

You can manually change this line: https://github.com/nextcloud/recognize/blob/main/lib/BackgroundJobs/ClusterFacesJob.php#L23

[GHBLoos]

I will test this and let you know the results.
I suppose it will be overwritten every time there is an update of the recognize app?

[marcelklehr]

Yes, that's the drawback. From my tests, AFAIR, a batch size of 10k should be fine for the recommended memory limits, though. I'm not sure why that's different in your case.

[GHBLoos]

Can I provide you any info from my server to figure out the reason?

My first impression is that the new batch size seems to work, but I will monitor it the next days. If it works, it would be great if this batch size could become a setting.

[GHBLoos]

I haven't received the initial error, but I did receive a lot of new errors. And when checking the 'faces' in the photo app, everything seems mixed up again. It looks like the faces that where manually combined have been separated again.

{"reqId":"EUfg89Yj1hFyJZFTPfD8","level":2,"time":"2025-04-11T01:11:07+00:00","remoteAddr":"","user":"--","app":"cron","method":"","url":"--","message":"Cron job used more than 300 MB of ram after executing job OCA\\Recognize\\BackgroundJobs\\ClusterFacesJob (id: 730433, arguments: {\"userId\":\"USER\"}): 746.6 MB (before: 10.8 MB)","userAgent":"--","version":"30.0.8.1","data":{"app":"cron"}}
{"reqId":"Q4tI3XPnvnts4FBHvJT6","level":2,"time":"2025-04-11T01:18:56+00:00","remoteAddr":"","user":"--","app":"cron","method":"","url":"--","message":"Cron job used more than 300 MB of ram after executing job OCA\\Recognize\\BackgroundJobs\\ClusterFacesJob (id: 730435, arguments: {\"userId\":\"USER\"}): 748 MB (before: 47.9 MB)","userAgent":"--","version":"30.0.8.1","data":{"app":"cron"}}

This error appears thousands of times

{"reqId":"BS2GeHks3Wwai7F4kPvO","level":3,"time":"2025-04-12T03:42:01+00:00","remoteAddr":"","user":"--","app":"PHP","method":"","url":"--","message":"Undefined variable $nodeDistance at /var/www/<cloud.domain>/html/apps/recognize/lib/Clustering/MrdBallTree.php#192","userAgent":"--","version":"30.0.8.1","data":{"app":"PHP"}}

[marcelklehr]

The $nodeDistance error is a known issue which has been hard to solve, see #965

The Cron job used more than 300 MB of ram warning can be ignored as the high RAM usage is expected.