Shutting down app that imports CacheManager kills entire instance


See this Community post for a description and a link to some minimal reproduction code. Upon disabling the test app, the product log shows multiple stack traces, all with this cause:

It turns out that shutting down the app caused the imported CacheManager to also be shut down (for the whole instance), resulting in the product being inoperative (e.g. cannot render any pages).




Laura Kolker
April 15, 2020, 12:18 PM

Thank you! Yes, I can see that one

Andrew S
April 14, 2020, 11:14 PM
Laura Kolker
April 14, 2020, 7:10 PM

No, I don’t have permission to see that

Andrew S
April 14, 2020, 2:13 AM
Laura Kolker
April 10, 2020, 2:52 PM

Andrew, can you update here (or provide a link to the public ticket we can watch) regarding when this documentation contradiction has been resolved? Good to know that ComponentImport annotation does not carry the same risk.
re: whether we’d know if disabling the plugin caused the entire product to crash - that seems pretty optimistic to me. Bugs that cause an entire system to fall over sometimes are inconsistent in their behaviors. And when the reason is because the documentation recommendations have changed since the plugin was developed, but the documentation is not up to date… It’s hard to feel confident about the situation. This is a pretty alarming bug tbh.

Not a bug


Andrew S


Dennis Fischer