Memory Exhaustion after deleting a registrant from a event

Deleting a registration is like deleting a page - after you delete it, it no longer exists, and clicking on a link to it gives a 404, which is the correct behavior. Thus the entry in the logs is expected.

Regarding the memory error, your report is not that clear, but I think you are saying that clicking on the Register link for the host entity (to create a new registration) gives a memory error, but only after some other registration is deleted. However, you also implied that you attempted to click on a link to a registration after deleting it - is that when you received the memory error? Can you clarify, your use of the phrase "registration link" is ambiguous - are you referring to a link to a deleted registration, or the Register link for doing a new registration. If you received the error after clicking on the stale link to the deleted registration, that would point to an issue with your 404 handling, and nothing to do with the registration module.

Thanks for the reply.

So the registration link I'm referring to is the registration field provided by the registration module. It's the field you would use on your content type that provides the link you would use for folks to register for an event.

Say like I've created two registration types: (Webinars and Trainings) and have the registration link on a event content type.

Then people sign up for events under the webinars registration type. If I delete one of those registrants, people can no longer register for the event under the Webinars registration type for that event , because of the memory time out. Clicking on the registration link causes the error to occur due to the deletion of a registrant.

All of this is using purely elements that are coming from the Entity Registration module, so I don't thin it's something outside the registration module.

If you have problems flagging down the issue, I can try to replicated the issue on a fresh Drupal install. It wouldn't be hard to recreate the issue.

I found the issue. So in one of my registration types, I changed the user field form display widget display from "autocomplete" to "chosen" and the registration module does not like that. (doesn't like the chosen module). So trying to register any event with that registration type give a memory timeout..

Changing it back to "autocomplete" fixes the issue.

Thanks, that makes more sense. I'll dig in and see what I can find.

I think you are likely running into this:

https://www.drupal.org/project/chosen/issues/3023506 →

Do you have a large number of users? If yes, the chosen module tries to load them all, so you could run out of memory. You could try increasing your PHP memory limit to see if that helps.