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.

Sign up for GitHub

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

Jump to bottom

Memory Leak on ProxyGenerator #1

Closed
corentinaltepe opened this issue Mar 13, 2019 · 1 comment
Closed

Memory Leak on ProxyGenerator #1

corentinaltepe opened this issue Mar 13, 2019 · 1 comment
Assignees
@corentinaltepe
Labels
bug Something isn't working

Comments

@corentinaltepe
Copy link
Owner

The proxy generator keeps track of the proxies it creates in order to pool them. Instanciating a new ProxyGenerator for every proxy creates a memory leak and performance issues. A single instance of proxyGenerator must be kept in order to resolve the memory leak and performance issues, when generating proxies with Castle.Core for logging.
@corentinaltepe corentinaltepe added the bug Something isn't working label Mar 13, 2019
@corentinaltepe corentinaltepe self-assigned this Mar 13, 2019
@corentinaltepe
Copy link
Owner Author

corentinaltepe commented Mar 14, 2019 •
edited
Loading

Fixed in latest commit 07d562c

@samolesen samolesen mentioned this issue Jul 22, 2021
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@corentinaltepe corentinaltepe

Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@corentinaltepe