Well done for finding it... sounds like one for open.silverstripe.org :)
We've moved the forum!
Please use forum.silverstripe.org for any new questions
(announcement).
The forum archive will stick around, but will be read only.
You can also use our Slack channel
or StackOverflow to ask for help.
Check out our community overview for more options to contribute.
- Previous 10 entries
- 1
- Page 22(current)
- 3
- Next 10 entries
Teamwork :-). http://open.silverstripe.org/ticket/6688
Hi Willr
I'm having some massive memory leak problems. When you say large dateobjectsets are we talking about 100, 1000, 100 000 . I'm not sure if the size of my site is causing a problem or the code. We have a lot of many to many relations with fairly large groups in the 100-1000 range and that doesn't seem excessive so I was planning on combing over my code and setting up php debugging software like you suggested but wanted to check with you first whether these are reasonable numbers.
Thanks
Will
ps any more news as to when 3.0 will be available? thanks again
vancouverWill I saw a leak of about 2k per data object (this was for research done for 2.3). I recommend installing XHProf and doing some research of your own!
ps any more news as to when 3.0 will be available? thanks again
At the moment the goal is still end of the year for another release (likely to be a final stage beta or rc)
Also remember with memory issues there is no garbage collection by default... I've added this during large dataobject manipulations to reclaim the memory and avoid the dread memory exhausted error...
http://silverstripe.org/general-questions/show/16988#post303671
I am now facing this problem and it really looks like what is happening as explained in this thread. I was doing some reorganizing of the pages and this came up!
I have tried upgrading to 2.4.6 but does not work. Is it something I need to change from the DB or some rebuilding of DB task I need to execute?
Please help as this is on my production. I can't edit the pages now.
Thanks in advance!
Just log in to your Database (phpmyadmin etc.) and edit the tables SiteTree and SiteTree_Live. Change the ParentID of the broken pages. For simplicity just change it to 0 (Root) and then move them around in the backend when you're done. You should be able to find the page you're looking for in the DB by looking at the URLSegment (same DB Table).
Can you explain the fix in detail ?
The problem is due to broken pages ? We have 20+ blogs and both the tables SiteTree_Live and SiteTree do not have any entries with HasBrokenLink = 1.
thanks
- Previous 10 entries
- 1
- Page 22(current)
- 3
- Next 10 entries