Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Caching and Security Trimming #118

Closed
zanfar opened this issue Dec 11, 2012 · 5 comments
Closed

Caching and Security Trimming #118

zanfar opened this issue Dec 11, 2012 · 5 comments

Comments

@zanfar
Copy link

zanfar commented Dec 11, 2012

Hi,

I am using your sitemap provider (which is very good) with security trimming and some node visibility for breadcrumbs in an mvc3 application running in .net 4.0, but am experiencing memory leaks, and was just wondering how the sitemap goes about caching data? Just need to check if the sitemap provider is causing any issues, as the memory leak is definitely more apparent when the sitemapprovider is included.

Any help greatly appreciated,

Thanks

Z

@waynebrantley
Copy link

Zanfar - would be a great contribution if you would profile the application and see if you can find any issues!??

@zanfar
Copy link
Author

zanfar commented Dec 11, 2012

I am doing so, unfortunately the memory leak seems to be in unmanaged code?? I have a load of debug information, but none that I can make sense at the moment. See http://stackoverflow.com/questions/13792072/memory-leak-in-mvc-web-application,

Thanks

Z

@zanfar
Copy link
Author

zanfar commented Dec 12, 2012

Hi Wayne,

Just read your comment on stackoverflow, you say you are noticing more out of memory exceptions, which scenarios do you experience them?

Thanks

Z

@NightOwl888
Copy link
Collaborator

I am interested to know if this issue still exists in v4: https://github.com/maartenba/MvcSiteMapProvider/tree/v4. It is feature complete, but not quite packaged up yet.

The caching in particular has been completely redesigned - you can even provide your own cache manager if you like.

@NightOwl888
Copy link
Collaborator

v4 is now in beta and we haven't had a single complaint about memory leaks or caching issues. I am marking this issue closed, as there won't be any more releases of v3 anyway.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants