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.
Follow-up to #2501441: Document SafeMarkup::set in AllowedTagsXssTrait::fieldFilterXss
Problem/Motivation
AllowedTagsXssTrait::fieldFilterXss() can add a lot of long strings into memory in the SafeMarkup list.
Proposed resolution
Free the memory, based on one of these:
Comments
Comment #1
xjmComment #2
xjmI think this one can be fixed with #2506195: Remove SafeMarkup::set() from Xss::filter().
Comment #3
cilefen CreditAttribution: cilefen commentedComment #4
star-szrWhat's the status here now that #2506195: Remove SafeMarkup::set() from Xss::filter() is in?
Comment #5
cilefen CreditAttribution: cilefen commentedThe Xss::filter() call in AllowedTagsXssTrait::fieldFilterXss() no longer adds strings to memory.
Comment #6
mgiffordThere doesn't seem to be anything to postpone this on anymore.
Comment #7
cilefen CreditAttribution: cilefen commentedI followed the call chain and it looks to be the case that we get something implementing SafeStringInterface but these calls do not bloat the safe strings list. Can someone else verify that?
Comment #8
BerdirYes, it's safe to say that this doesn't happen anymore I think.