[wp-trac] [WordPress Trac] #36455: Call opcache_reset() after plug-in, theme or core update

[WordPress Trac]

#36455: Call opcache_reset() after plug-in, theme or core update
-------------------------------------------+---------------------------
 Reporter:  nigro.simone                   |       Owner:  mikeschroder
     Type:  enhancement                    |      Status:  assigned
 Priority:  normal                         |   Milestone:  5.5
Component:  Upgrade/Install                |     Version:
 Severity:  normal                         |  Resolution:
 Keywords:  has-patch needs-testing early  |     Focuses:
-------------------------------------------+---------------------------

Comment (by nextendweb):

 Replying to [comment:81 mikeschroder]:
 > I'm trying to think of cases where invalidating deleted files would be
 important. Direct requests to them that are started from an already loaded
 page (before the update), perhaps? Are there any common cases y'all have
 seen?

 I can not think any case where not invalidating deleted files would result
 in error. The idea behind this, to release opcache memory for the files
 which are deleted. Probably opcache itself do garbage collection for the
 long time not used files. If that is the case, there is no need to
 invalidate deleted files.

 It is worth to mention that opcache will resets itself completely when it
 reaches the {{{opcache.max_accelerated_files}}} limit, but I'm not sure
 how {{{opcache_invalidate}}} affects this limit:
 [https://serverfault.com/questions/730953/php-opcache-is-resetting-cache-
 automatically]

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/36455#comment:82>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform