XF 2.1 Fatal error regarding memory

sixlxvi

Active member
I just got this error a few times about memory. There shouldn't be a reason why my site is suddenly using increased memory. I was playing with CSS in templates today but I doubt that has to do with this?

Code:
ErrorException: Fatal Error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 266240 bytes) src/vendor/oyejorge/less.php/lib/Less/Environment.php:159
Generated by: Unknown account Aug 17, 2020 at 1:47 PM
Stack trace
#0 [internal function]: XF::handleFatalError()
#1 {main}
Request state
array(4) {
  ["url"] => string(141) "/css.php?css=public%3Anormalize.css%2Cpublic%3Acore.less%2Cpublic%3Aapp.less&s=14&l=1&d=1597686441&k=9df9bc9b2a89930fb56d759d99b3fabab547ddc4"
  ["referrer"] => string(46) "https://tacoma3g.com/forums/rad-people-club.2/"
  ["_GET"] => array(5) {
    ["css"] => string(53) "public:normalize.css,public:core.less,public:app.less"
    ["s"] => string(2) "14"
    ["l"] => string(1) "1"
    ["d"] => string(10) "1597686441"
    ["k"] => string(40) "9df9bc9b2a89930fb56d759d99b3fabab547ddc4"
  }
  ["_POST"] => array(0) {
  }
}

And here is another one about a template that I don't think I touched. It brings up a forum called Rad People Club which is a private forum that I moved from one parent forum to another parent forum.

Code:
XF\CssRenderException: Error rendering template public:core.less: ParseError: missing closing `}` in public:core.less on line 17148, column 2 (on or near line 17148) src/XF/CssRenderException.php:87
Generated by: Unknown account Aug 17, 2020 at 1:38 PM
Stack trace
 17145 |     }
 17146 |
 17147 |     &--newIcon
*17148*|     {
 17149 |         color:DarkGoldenRod ;
 17150 |     }
 17151 | }
------------

#0 src/XF/CssRenderer.php(408): XF\CssRenderException::createFromLessException(Object(Less_Exception_Chunk), 'public:core.les...', '// Note that th...')
#1 src/XF/CssRenderer.php(342): XF\CssRenderer->renderToCss('public:core.les...', '// Note that th...')
#2 src/XF/CssRenderer.php(250): XF\CssRenderer->renderTemplate('public:core.les...', NULL)
#3 src/XF/CssRenderer.php(116): XF\CssRenderer->renderTemplates(Array, Array, Array)
#4 src/XF/CssWriter.php(53): XF\CssRenderer->render(Array)
#5 css.php(30): XF\CssWriter->run(Array, 14, 1, '9df9bc9b2a89930...')
#6 {main}

-------------

Previous Less_Exception_Chunk: ParseError: missing closing `}` in anonymous-file-0.less on line 17148, column 2
17146|     
17147|     &--newIcon
17148|     {
17149|         color:DarkGoldenRod ;
17150|     }
17151| } - src/vendor/oyejorge/less.php/lib/Less/Parser.php:677
#0 src/vendor/oyejorge/less.php/lib/Less/Parser.php(621): Less_Parser->GetRules(NULL)
#1 src/vendor/oyejorge/less.php/lib/Less/Parser.php(449): Less_Parser->_parse()
#2 src/XF/CssRenderer.php(404): Less_Parser->parse('// Note that th...')
#3 src/XF/CssRenderer.php(342): XF\CssRenderer->renderToCss('public:core.les...', '// Note that th...')
#4 src/XF/CssRenderer.php(250): XF\CssRenderer->renderTemplate('public:core.les...', NULL)
#5 src/XF/CssRenderer.php(116): XF\CssRenderer->renderTemplates(Array, Array, Array)
#6 src/XF/CssWriter.php(53): XF\CssRenderer->render(Array)
#7 css.php(30): XF\CssWriter->run(Array, 14, 1, '9df9bc9b2a89930...')
#8 {main}
Request state
array(4) {
  ["url"] => string(141) "/css.php?css=public%3Anormalize.css%2Cpublic%3Acore.less%2Cpublic%3Aapp.less&s=14&l=1&d=1597685886&k=9df9bc9b2a89930fb56d759d99b3fabab547ddc4"
  ["referrer"] => string(46) "https://tacoma3g.com/forums/rad-people-club.2/"
  ["_GET"] => array(5) {
    ["css"] => string(53) "public:normalize.css,public:core.less,public:app.less"
    ["s"] => string(2) "14"
    ["l"] => string(1) "1"
    ["d"] => string(10) "1597685886"
    ["k"] => string(40) "9df9bc9b2a89930fb56d759d99b3fabab547ddc4"
  }
  ["_POST"] => array(0) {
  }
}
 

sixlxvi

Active member
Are you still getting the errors?
Not currently, probably because:

1) My server provider increased my memory, although I don't think that was necessary because the server already has specs that are overkill for my forum.

2) Whatever caused it was because of me editing some styling in templates or moving that sub-forum that has very specific permissions set to it. And since those two things are done now, I guess the server error is also done?
 
Top