Closed baileyherbert closed 6 years ago
Actually, turning back the memory limit to the default of 2048 MB fixed the issue. Perhaps there is an internal problem with how this is applied when modified by the user?
Hmmm, this should be working properly in the Atom package; it is passed as an override on the command line via the -dmemory_limit=<your_value>M
flag.
You could try setting another value and then looking at your process manager to see if it is correctly applied, I think (at least if said process manager shows command line parameters as well).
I just performed a fresh install with 4.4.0 and was trying to figure out why the plugin wasn't working. Console showed some socket connect errors. Turns out this is the likely culprit (error_log in the server dir).
2097152
bytes is a mere 2MB, vastly smaller than the 4096 MB I configured in the plugin (and I've restarted Atom/reinstalled the server multiple times).The configured memory limit in my php.ini is at
256M
, so I'm not sure what's going on here? Any advice to get this thing spinning?