Fatal error: Allowed memory size of xxxxx bytes exhausted

Hello Composr Community, it's been a while for me, I trust this finds everyone well!

Been a long time since I've seen this error! Having not seen any recent posts describing this same issue, at this point I consider it a curiosity rather than a big problem.  

Haven't had to edit much content on the Composr sites I have deployed as they've been setup for some time now and I often just edit remotely. I recently had cause to setup a proof of concept for a potential new deployment to assist a volunteer organization. 10.0.46 was the version used and I initially loaded into an Ubuntu Server VM 23.10 with all the defaults as far as versions of LAMP that were installed. Unfortunately I can't remember if the issue appeared in this setup or not as I had reason to change my platform to accommodate another project so I ended up with 20.04 and php 7.4.

The issue does not appear right away but once it does it does not go away. The site is navigable, content visible but any attempts to launch and edit or even the template/css popup from the footer results in the error. The only time I can force it away is to edit an empty page. Once content gets back in again the error reappears. 22.04 and 7.4 produces the same.

As is often the case with this error, raising memory does not help. I decided to see if I could recreate on a test machine I have here that I putter away on. It has an upgraded 10.0.46, php7.4. Working with the site for a short while and voila! up comes the error, odd.

Decided to check the two sites I have on a hosting platform: attempts to edit result in a 503 now being thrown.

Going forward: has anyone else experienced this? Anything you are aware of Patrick? If not, I'll setup my full test environment here and see if I can narrow it down. The only commonality at this point is 10.0.46 and PHP7.4.

Thanx!

It's this bug:

0005640: Editing home page results in an infinite loop in diff - Composr CMS feature tracker

  Many humble apologies for wasting your time Patrick, I completely forgot to check Mantis! *facepalm*

Thanx for the reply!

No worries! I (hopefully) fixed it in the latest 10.0.47 patch release. Well, rather, I took the v11 version of the diff code and ported it to v10 since the v11 version was not experiencing this bug.

I can confirm the fix does remove this issue…      

I can confirm that it is fixed in the installation that I noticed it in the first place post upgrade to 10.0.47. I'll upgrade my other sites over the next day or so to verify those as well.

As an FYI, one other thing I noticed that with the exception of one of the pages, all the others I was testing with (6 different ones across 3 10.0.46 installations) were fine for the first one or two edits and then pooched after that.

Thanx for the fix up, appreciated!

SoccerDad said

As an FYI, one other thing I noticed that with the exception of one of the pages, all the others I was testing with (6 different ones across 3 10.0.46 installations) were fine for the first one or two edits and then pooched after that.

From “Post #9,728”, 19th March 2024, 6:23 pm

That was to be expected. Upon the first edit, there was nothing to diff since the page was never edited before.

Good to hear it's working now.