Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

supertable field not saving, causing memory/backend crash. #292

Closed
wihodges opened this issue Aug 8, 2019 · 2 comments
Closed

supertable field not saving, causing memory/backend crash. #292

wihodges opened this issue Aug 8, 2019 · 2 comments

Comments

@wihodges
Copy link

wihodges commented Aug 8, 2019

Description

Ok so super strange issue, where all entries with supertable field no longer save. When save button is pushed craft backend goes down causing 504 timeout. I'm not sure what is the cause of this, I recently updated Craft to latest version.

The issue is happening on local valet and production. I don't think it's a memory problem even though the 'PHP Fatal Error' says: Allowed memory size of 268435456 bytes exhausted (tried to allocate 528384 bytes) in /home/repopath/craftcms/cms/src/elements/db/ElementQuery.php on line 2073. I also don't see any clear log entry erroring. I think it's causing a massive spike in resources. The closest related issue I could find is craftcms/cms#4459 (comment) but looks like that was solved.

The only thing I can narrow down is that it's only affected by supertable field being present on entry.

Also strange is I have another site that leverages Supertable plugin and updated to latest version of craft and it's working just fine. So really not clear, what is going on.

Steps to reproduce

  1. Open entry with supertable field.
  2. Make a change and try to save.

Additional info

  • Plugin version: 2.2.1
  • Craft version: 3.2.9
@wihodges
Copy link
Author

wihodges commented Aug 8, 2019

Ok so gets a bit stranger, I finally narrowed it down to another plugin, Activity Log, in conjunction with supertable. When enabled Activity log seems to crush the backend. So not sure why as I have Activity log and Supertable working together in another site and they seem to work fine. Not sure why other entries work without supertable...

@wihodges wihodges closed this as completed Aug 8, 2019
@engram-design
Copy link
Member

@wihodges Thanks for this, I've not tried Activity Log, but will look into it, and if there's anything I can do

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants