Ayende @ Rahien

Kasi Prasad commented on Production issue: ASP.Net Cache kills the application

Sat, 01 Dec 2012 01:12:55 GMT

My comment got clipped: < caching enabled="false" />

Kasi Prasad commented on Production issue: ASP.Net Cache kills the application

Sat, 01 Dec 2012 01:10:57 GMT

Sounds like a job for DebugDiag. You might just try:

smcintire commented on Production issue: ASP.Net Cache kills the application

Tue, 20 Nov 2012 13:32:50 GMT

Are you using iis 7.5? if so, is the application running in integrated or classic pipe (and does it happen in both)? which version of .net are you running in? can you change the max cache size in your iis config?

Francisco Gómez commented on Production issue: ASP.Net Cache kills the application

Mon, 19 Nov 2012 15:32:49 GMT

Perhaps the exception of the log is not the cause but a restart of the application for memory problems (App Domain recycling). Enable tracing "Application Lifetime Events" to see what´s going on before the exception.

Ayende Rahien commented on Production issue: ASP.Net Cache kills the application

Mon, 19 Nov 2012 08:15:29 GMT

Andrew, No, there is only one site on this machine.

Rory Primrose commented on Production issue: ASP.Net Cache kills the application

Sun, 18 Nov 2012 23:02:19 GMT

You might not be putting something in the cache in your code, but you may be using another component that does.

Andrew commented on Production issue: ASP.Net Cache kills the application

Sun, 18 Nov 2012 22:13:04 GMT

Is it possible you have another website in the same app pool which is responsible for the crash?

Remco Ros commented on Production issue: ASP.Net Cache kills the application

Sun, 18 Nov 2012 18:42:37 GMT

Pretty awesome that you can post questions like this, and get responses faster then when we post a question on stackoverflow.. epic, and well deserved ofcourse.

Chris Shaffer commented on Production issue: ASP.Net Cache kills the application

Fri, 16 Nov 2012 20:38:47 GMT

Using DisableMemoryCollection seems like a bad/dangerous idea - then if some bit of the code actually is using it (whether that bit of code is something built into .Net, a 3rd party library, or the code), then you risk wasting memory and the out of memory issue mentioned in the linked answer. And you just have to remember to be careful with the cache in the future (as does anyone that happens to inherit the project in the future). Kevin Dente's suggestion seems the most appropriate as a fix for the symptom - perhaps add on a memory dump when the exception occurs so you can try to get down to the root cause later on...

Steven Casey commented on Production issue: ASP.Net Cache kills the application

Fri, 16 Nov 2012 20:23:30 GMT

did you try disablememorycollection as Khalid suggested? stackoverflow also suggests the same http://stackoverflow.com/questions/6843343/disable-asp-net-cache

Ayende Rahien commented on Production issue: ASP.Net Cache kills the application

Fri, 16 Nov 2012 20:05:01 GMT

Mystical, Does it matter if you call each other or it is a loop? It is the same basic principal.

Ayende Rahien commented on Production issue: ASP.Net Cache kills the application

Fri, 16 Nov 2012 20:04:43 GMT

Kevin, Thanks, that is what we might do

Kevin Dente commented on Production issue: ASP.Net Cache kills the application

Fri, 16 Nov 2012 18:25:01 GMT

It's not a fix, but if you want to stabilize things temporarily you could try reverting to the old unhandled exception policy using the legacyUnhandledExceptionPolicy flag in web.config http://msdn.microsoft.com/en-us/library/ms228965.aspx

Chris Shaffer commented on Production issue: ASP.Net Cache kills the application

Fri, 16 Nov 2012 18:10:11 GMT

Stab in the dark for a fix and not an explanation - Maybe put something in the cache every once in a while so the cleanup thread has something to do.

Khalid Abuhakmeh commented on Production issue: ASP.Net Cache kills the application

Fri, 16 Nov 2012 17:01:24 GMT

Drastic times call for Drastic measures

Ayende Rahien commented on Production issue: ASP.Net Cache kills the application

Fri, 16 Nov 2012 16:59:42 GMT

Poul, I went over the code, there is nothing that touches the cache, yes. And this error happened twice in two weeks period in a heavily occupied prod system.

Poul Foged commented on Production issue: ASP.Net Cache kills the application

Fri, 16 Nov 2012 16:57:44 GMT

Ok, a handler that spits out cache.items then. So you're 100% sure its empty before the crash? It just feels like a lot of the suggestions here are hacks ...

Ayende Rahien commented on Production issue: ASP.Net Cache kills the application

Fri, 16 Nov 2012 16:51:49 GMT

Poul, * when this happens, it kills the process, no way to get it. * there is no aspx there, it is just a handler that gets all requests.

Poul Foged commented on Production issue: ASP.Net Cache kills the application

Fri, 16 Nov 2012 16:48:36 GMT

I know, but it can't be empty right? I'd throw up a .aspx that just prints out Cache.Items ....

Ayende Rahien commented on Production issue: ASP.Net Cache kills the application

Fri, 16 Nov 2012 16:41:36 GMT

Khalid, That is my nuclear option, I would REALLY not do that.

Ayende Rahien commented on Production issue: ASP.Net Cache kills the application

Fri, 16 Nov 2012 16:40:59 GMT

Poul, This happens in prod. And I checked, the entire code base doesn't use the cache.

Poul Foged commented on Production issue: ASP.Net Cache kills the application

Fri, 16 Nov 2012 16:38:57 GMT

Something _must_ be in the cache, try taking a look at Cache Items

Khalid Abuhakmeh commented on Production issue: ASP.Net Cache kills the application

Fri, 16 Nov 2012 16:31:53 GMT

Did you try the configuration settings? If they didn't you can also do a little reflection trick that looks like it would work. get the CacheManager using reflection and alter the _timer private property. It is currently using this below. this._timer = new Timer(new TimerCallback(this.PBytesMonitorThread), (object) null, this._currentPollInterval, this._currentPollInterval); You could just modify it to be infinite. this._timer = new Timer(new TimerCallback(this.PBytesMonitorThread), (object) null, this._currentPollInterval, int.MaxValue); not saying you won't have the issue pop up again, but it will happen far into the future.

Ayende Rahien commented on Production issue: ASP.Net Cache kills the application

Fri, 16 Nov 2012 15:46:46 GMT

Remi, No, I do not.

Rémi BOURGAREL commented on Production issue: ASP.Net Cache kills the application

Fri, 16 Nov 2012 15:40:09 GMT

you can also override string GetOutputCacheProviderName(HttpContext context) In your httpapplication for loggin wich request try to acces to the asp.net cache.

Petar Repac commented on Production issue: ASP.Net Cache kills the application

Fri, 16 Nov 2012 15:39:16 GMT

From Reflector: internal long TrimCache(int percent) { long num = 0L; Dictionary.KeyCollection keys = null; lock (this._lock) { if ((this._cacheInfos != null) && (this._cacheInfos.Count > 0)) { keys = this._cacheInfos.Keys; } } if (keys != null) { foreach (MemoryCache cache in keys) { num += cache.Trim(percent); } } return num; } "_cacheInfos" is protected by the lock, but then "keys" points to "_cacheInfos" and is not protected by the lock, so Dictionary can change ant any time.

Rémi BOURGAREL commented on Production issue: ASP.Net Cache kills the application

Fri, 16 Nov 2012 15:34:42 GMT

By default asp.net use the cache for every scriptressource, are you using any ?

Ayende Rahien commented on Production issue: ASP.Net Cache kills the application

Fri, 16 Nov 2012 15:25:32 GMT

Wyatt, This isn't output caching, this is the CacheManager getting nasty.

Wyatt Barnett commented on Production issue: ASP.Net Cache kills the application

Fri, 16 Nov 2012 15:21:00 GMT

2nding killing the ASP.NET cache dead -- if you need caching use a caching proxy. To kill the output cache dead, you need to disable the module in the web config. To get midieval you can also remove it from the root web.config in the %SYSTEMROOT%\Microsoft.NET\Framwork\$VERSION\CONFIG\web.config file.

Khalid Abuhakmeh commented on Production issue: ASP.Net Cache kills the application

Fri, 16 Nov 2012 15:19:58 GMT

Sorry, the comment was stripped for some reason. [caching] [cache disableExpiration="true" disableMemoryCollection="true" />] [/caching]