You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I'm having a very strange problem using this library, possibly a memory leak?
In my application, I need to create multiple ribbon windows, which contain some ribbon buttons and commands.
Defined as follows:
I need to create a lot of windows like this and when they are closed, in VS memory monitoring tool I found that the window object is not being recycled. After reading the source code and doing some tests, I found that there are three situations in which the window can be recycled.
Do not set commands for ribbon buttons;
In the window closed event, set the command to null;
Remove the IconPresenter from the button template.
I didn't find the relation between IconPresenter and Command from the code.
This was caused by wrong code in the IconPresenter which caused all IconPresenters, that got disabled at least once, to be held in memory by the GrayscaleEffect that's being used in IconPresenter.
Hi, I'm having a very strange problem using this library, possibly a memory leak?
In my application, I need to create multiple ribbon windows, which contain some ribbon buttons and commands.
Defined as follows:
I need to create a lot of windows like this and when they are closed, in VS memory monitoring tool I found that the window object is not being recycled. After reading the source code and doing some tests, I found that there are three situations in which the window can be recycled.
I didn't find the relation between IconPresenter and Command from the code.
Here is my test project:
Ribbon.MemLeakTest-main.zip
Environment
The text was updated successfully, but these errors were encountered: