NuCache "panic"
See original GitHub issueUnder heavy multithreaded loads, or on some yet unknown situations, NuCache can panic in ContentStore.CreateSnapshot()
. It has been reported once by Shannon in september, 2018 - then again by Bjarke a few months later - so it’s quite rare but happens nevertheless.
And then there is this Our thread so it definitively is a thing.
Issue Analytics
- State:
- Created 5 years ago
- Comments:10 (6 by maintainers)
Top Results From Across the Web
disabling nucache under umbraco 8
My question would be, how to disable NuCache. ... and well, these 'panic' messages happen in NuCache when a situation that just is ......
Read more >Umbraco Disable NuCache Database Composer
i have a problem (in log file): "An unhandled exception was thrown by the application.","@l":"Error","@x":"System.IO.
Read more >too orangey for crows
The biggest risk is probably NuCache in terms of impact and size of change... all you can point to here is the 'NuCache...
Read more >AppDomains, Threads, CultureInfos And Paracetamol - ZpqrtBnk
NuCache essentially is one thread-safe dictionary using the content identifier as a key. For each identifier, it contains a pair: the draft (unpublished) ......
Read more >Untitled
... Valigia semirigida 4 ruote, Brufolo dietro la nuca che non passa, Allestimento r ... Banco napoli sede legale, Uomini di galilea spartito,...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Please comment here, yes, now that it is a confirmed issue.
FWIW, I have been able to reproduce the panic in a unit test - now to fix it…
Thanks for the feedback. It seems that the original issue has been fixed, so I am moving this issue to review, so the fix can be merged and part of a next release.
Now about that new exception… I have created #4998 to track it. Let’s discuss it there.