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 #2408371: Proxies of module interfaces don't work
Problem/Motivation
- addPSR4() during test runs ads more and more PSR-4 data to the autoloader, which is a small memory leak.
Proposed resolution
- Use setPSR4() instead of addPSR4(), because there is no way to reset the autoloader's state and the composer autoloader itself is a singleton.
Remaining tasks
- Do it
User interface changes
- None
API changes
- None
Data model changes
- None
Comment | File | Size | Author |
---|---|---|---|
#3 | use-setpsr4-instead-of-addpsr4-2513344-1.patch | 1.32 KB | scythian |
Comments
Comment #2
scythian CreditAttribution: scythian at FFW commentedComment #3
scythian CreditAttribution: scythian at FFW commentedI've found only two addPSR4() inside tests, which changed to setPSR4().
Comment #4
davidhernandezComment #16
smustgrave CreditAttribution: smustgrave at Mobomo commentedThis issue is being reviewed by the kind folks in Slack, #need-reveiw-queue. We are working to keep the size of Needs Review queue [2700+ issues] to around 200, following Review a patch or merge require as a guide.
Changing to a task as this seems like an improvement.
At this time we would need a D10.1.x patch or MR for this issue.
This may also require framework manager review?