1. Create a content type with many fields, including a link field.
2. Create a few items of content.
3. Enable devel and Views with autopreview.
4. Create a view and load the fields individually.
5. Add a Views PHP field with this output code: 

<?php
print_r($data);
?>

The Views automatic preview is likely to freeze your computer. :) If not, Devel will report some fantastic memory usage (on my system it was over 400MB for a View with a single item).

Sorry for the scarce details but I'm travelling at the moment. I'll be back at the weekend and will follow up. Please let me know if you can reproduce this issue, there is a slight chance that this is not a bug but something specific to my site.

However, reverting to Link 1.0 seems to have solved my problem.

Comments

joemaine’s picture

joemaine commented

Not sure if this is a similar issue...but when trying to add a link field (7.x-1.1) to a content type with multiple term references I receive the following:

Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 78 bytes) in /home/xxx/public_html/sites/all/modules/token/token.pages.inc on line 71

joemaine’s picture

joemaine commented

Reverting to Link 1.0 allows me to access the edit tab on the Link Field in the content type. The page takes a bit of time to load a script (longer in IE10 than Chrome)

I can't access the edit tab with Link 1.1 installed. I increased the memory to 512 and still received errors:
Fatal error: Allowed memory size of 536870912 bytes exhausted (tried to allocate 67048893 bytes) in /public_html/devsite/includes/database/database.inc on line 2139

geraldito’s picture

geraldito commented

Same memory issue here when trying to open edit tab on the Link Field.

skoehn180’s picture

skoehn180 commented

I was having this issue as well and in combination with issues with a couple of other modules (pathauto, entity token) was led to the Token Tweaks module.

Enabling that and setting the "Maximum depth limit" to 2 resolved my Link issue as well as the others.

weddigen’s picture

weddigen commented
Issue summary: View changes

Hi, the Token Tweaks with Max Depth = 2 solved my Memory Issue with Link,

thanks a lot for the advice!

dqd’s picture

dqd
Location London | N.Y.C | Paris | Hamburg | Berlin
commented
Priority: Major » Normal
Status: Active » Postponed (maintainer needs more info)

Can somebody chime in with more details? Any loop or hock somewhere in code which causes this? I can't reproduce it here and it seems to come up in combination of other modules and link settings in your set ups, otherwise there would be more reports on this, isn't it?

Please give more details to find the constipation. Otherwise we rather should designate it as a feature request to make link module more lightweigt again. Yes - It became quite big over the years with all the other feature requests blowing the code.

dqd’s picture

dqd
Location London | N.Y.C | Paris | Hamburg | Berlin
commented
Title: Major memory issue in Link 1.1 with Views » Profuse memory load by using Link module with Views
Issue tags: +memory issues
interx’s picture

interx commented

I looked into this before I found this issue at #2295071: Recursion in field formatter with views.

dqd’s picture

dqd
Location London | N.Y.C | Paris | Hamburg | Berlin
commented

awesome. thx interX. Can anyone else review this over there?

dqd’s picture

dqd
Location London | N.Y.C | Paris | Hamburg | Berlin
commented
Issue summary: View changes
Related issues: +#2295071: Recursion in field formatter with views