[CSHARP-300] Memory Issue in Cursor / IIS Web Application only Created: 08/Aug/11  Updated: 20/Mar/14  Resolved: 19/Jul/12

Status: Closed
Project: C# Driver
Component/s: None
Affects Version/s: 1.1
Fix Version/s: 1.6

Type: Bug Priority: Major - P3
Reporter: Alice Mauschberger Assignee: Sridhar Nanjundeswaran
Resolution: Cannot Reproduce Votes: 2
Labels: c#, driver
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Windows 2008 R2 x64, Windows 7 x64 (latest SP & Updates installed), IIS 7.5, .Net 4.0


Attachments: Zip Archive MongoDriverTest.zip    

 Description   

I'm using MongoDB 1.8.2 and mongo-csharp-driver 1.1.0.4184 (IIS 7.5/.Net 4.0 x64).
The Web Server memory is increasing after every select (about 10,000 results in the cursor) -> which leads very fast to > 2 GB memory usage.
The memory is never released anymore and only an application pool recycle can free the memory.
It seems that Console Applications and Web Applications hosted in VS built in Dev Web Server don't have the Problem.

Sample Web Application is attached to reproduce the problem.



 Comments   
Comment by Robert Stam [ 19/Jul/12 ]

Changing status from Closed to Resolved.

Comment by Robert Stam [ 19/Jul/12 ]

Reopening to change status from Closed to Resolved.

Comment by Robert Stam [ 10/Jul/12 ]

We have made several attempts to reproduce this and have not been able to.

So we are going to close the issue. If there actually is an issue perhaps someone will file a new JIRA (or re-open this one) with additional information that will make it possible for us to reproduce this.

Comment by Sridhar Nanjundeswaran [ 13/Mar/12 ]

Thank you for your test code. I am unable to cause the memory used by the w3wp process to grow without limits. I am using IIS 7.5. I ran multiple inserts and have 250K documents. I then run Select multiple times. With the select loop selecting 250K docs it grows to around 750MB max. Subsequent page reloads sometimes even cause the memory to dip to about 500MB. When running this within the Dev web server it seems to cap around 100MB and a lot lesser in a command line version of it.
I am going to investigate why within IIS the memory usage is so much higher and will post back with updates.

Comment by AndrewK [ 25/Oct/11 ]

have the mitigating circumstances been identified yet? does this apply to all cursors or is there something specific causing this?

thanks

Generated at Wed Feb 07 21:36:25 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.