Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.One of my Page nodes links to 3 Webform nodes: that's the only node on my site that I've found so far which produces this problem. I get a WSOD caused by an 'out of memory' error. If I disable Internal Links, the page loads. memory_limit is 256MB.
When Suhosin is enabled it's reported as a segmentation fault, which is quite worrying.
The out of memory error is sometimes thrown by includes/bootstrap.inc or includes/database/select.inc, but usually by modules/filter/filter.module (on various lines).
What's the best way to debug this further?
Comments
Comment #1
LoMo CreditAttribution: LoMo commentedThat's baffling. I haven't seen anything like that, myself, but perhaps there is something special about your case? Perhaps if you give me the steps to replicate the issue, I can dig in and try to find a solution. I guess I would need to know what other modules you have active. You only have this problem if the links are to Webform nodes? And you have other pages with links which are getting properly replaced without issue?
If you have a lot of internal links on your site and don't want to have to disable the module, I suppose the easiest workaround would be to manually set the links and titles for the three links on that one page, which should make the filter ignore those links (i.e. not attempt to seek titles and/or URL aliases). And, in the unlikely event the problem persists, even with those links manually replaced, that could offer further clues.
Comment #2
LoMo CreditAttribution: LoMo commentedIf anyone can reproduce this issue or can explain how to, please do so. Until then I'm closing this as "cannot reproduce" and would be happy to resolve this if anyone knows why this might happen and can provide a patch or some idea of what to do.
Comment #3
berenddeboer CreditAttribution: berenddeboer commentedI have exactly the same problem here, but before getting the out of memory I get the:
Fatal error: Maximum function nesting level of '150' reached, aborting! Fatal error: Maximum function nesting level of '150' reached, aborting!
as I have xdebug enabled. Could this be recursion??
Call stack below:
Comment #4
berenddeboer CreditAttribution: berenddeboer commentedUpdate: I only get this with 1.2. I just reverted to 1.1 and the problem disappears.
Comment #5
LoMo CreditAttribution: LoMo commentedI think I know what's going on. The main difference between the releases was adding "better" support for multi-lingual. I'll try to get this fixed this weekend.
Comment #6
martysteer CreditAttribution: martysteer commentedI'm getting this too, though it only just surfaced when I updated other, (what I thought to be) seemingly unrelated modules - context_disable_context, token, redirect, wysiwyg). Switching off the intlinks input filter stops it happening.
I was getting segmentation faults in the server logs, and 'Error 324 (net::ERR_EMPTY_RESPONSE): ' errors using chrome. Only on recently edited pages. The drupal content listing and any views which used these recently edited nodes also caused the segfault.
Searching on these sent me down the path of considering checking MTU's, caching, boost and entity based possible issues. Deleting the node and it's field values manually from the DB, recreating it, etc. etc. My sysadmin also output all errors to the logs but in the end it was the Devel query log which pointed to an infinite node load loop (if only I looked there first!).
Reverting to 1.1 fixes the issue for me too.
ps. Perhaps intlinks could be reimplemented as a pathologic hook (new feature in 7.x-2.4).
Comment #7
kabojnk CreditAttribution: kabojnk commentedI got the same problem, too. I had to revert back to 1.1. Spent a good 8 hours trying to figure out what was causing things to crash, however.
Comment #8
LoMo CreditAttribution: LoMo commentedI'm changing this to a bug report and marking it "needs review".
The language logic added in 7.x-1.2 has been removed in 7.x-1.3, which also includes some other bug fixes (some minor improvements which were also in 7.x-1.2, plus support for links which include a query, etc).
Language logic is now in the 7.x-2.x branch, which hopefully has also got this bug fixed. When multilingual support is a bit better, we'll make a stable 7.x-2.0 release, but those who are using Internal links on monolingual sites should avoid the 2.x branch since the extra language logic in this branch won't help anything.
I'm sorry I did not realize how much trouble the 7.x-1.2 release was causing some of you and apologize for the delay in getting this resolved. Please do let me know if this issue persists in either branch and please avoid 7.x-1.2
Comment #9
mkalkbrennerHappened here in 7.x-2.x
Comment #10
Anonymous (not verified) CreditAttribution: Anonymous commentedWe recently experienced this using version 7.x-1.3. Unfortunately, we had the same problem as kabojnk on #7 with it taking several hours to pinpoint the problem.
Comment #11
Saratt CreditAttribution: Saratt commentedI think I am having the same issue too. All I did was create a test page with just "test" in the body field and after publishing it, edited it and added a link to it that links to the same page(www.domain.com/test) something like
<a href="/test">test</a>. And the page never saves, and also the find content page never loads too i.e www.domain.com/admin/content page never loads.I would like to know if anyone have similar issues and have found a workaround.
Thanks.
Comment #12
mkalkbrennerPlease try 7.x-2.x-dev instead and report the results. I replaced the critical calls to node_load / entity_load by an EntityFieldQuery. That should reduce the memory usage and avoid endless recursions.
Comment #13
Saratt CreditAttribution: Saratt commented@mkalkbrenner: Installed 7.x-2.x-dev and I dont see the issue that I mentioned in the comment#11 above anymore. The page and admin/content load fine without any issues. Will report any issues if I come across one.
Thank you.
Comment #14
rp7 CreditAttribution: rp7 commentedFYI: I was having this problem in 7.x-1.3 on a Webform node which contained an internal link to itself. Removing the link fixed it for me.
Comment #15
dman CreditAttribution: dman commentedThis got me today.
Also using 7.x-1.3, Also took several hours of tracing segfaults and a site I couldn't get back online at all after clearing the cache.
Also may be related to multilingual - using entitytranslation (field-based)
Possibly related, I am using viewfield that has historically managed to set up infinite loops when a node attaches a view that lists teasers that need loading that (incorrectly IMO) does a full load of the attached views for THEM and then ... :-(
But yeah, I pulled the DB down to a dev system and extracted a stack trace the same shape as #3
I'll compare with 7.x-1.x dev now... oh, 7.x-2.x ? OK then (can you put a release up on the project page for that?)
Comment #16
mkalkbrennerI did not spent that much time on this module, but I think a 7.x-2.x is ready for a first alpha release.