@SeriousM

Please read the comment on c72a992

@SeriousM

Be aware! Race condition ahead! The call to IsAlive is more or less just a check if the Target is available or not. The later call to Target might …

@SeriousM

Your fix indicates that we have multiple weak references for the same target. Could you fix the root issue instead the symptom please? Am 24.06.201…

@SeriousM
@SeriousM

It would be great if you could also fix #52 / #53 for this release as it leaks memory when translating collapsed elements. @MrCircuit is currentl…

@SeriousM
Fix issue #52 - Memory leak
@SeriousM

#62 is fixing this problem.

@SeriousM

Alright @ctusch, @MrCircuit is fixing the leak on the XAMLMarkupExtensions side, I already fixed it on WPFLocalizationExtension. Just hang on until…

@SeriousM
Memory leak when localizing a ContextMenu
SeriousM deleted branch memoryleak at SeriousM/WPFLocalizationExtension
@SeriousM
@SeriousM
fix the memoryleak by using weak references
1 commit with 157 additions and 70 deletions
@SeriousM
Memory leak when localizing a ContextMenu
@SeriousM
fix the memoryleak by using weak references
1 commit with 157 additions and 70 deletions
SeriousM commented on pull request MrCircuit/XAMLMarkupExtensions#5
@SeriousM

@MrCircuit: please update the nuget package update the reference on wpflocalizeextension release new package there close bug SeriousM/WPFLocalizat…

@SeriousM
Fixing memoryleak
1 commit with 27 additions and 20 deletions
@SeriousM
@SeriousM

Found the issues which spans over XAMLMarkupExtensions and WPFLocalizationExtension. How important is the fix for you @ctusch?

@SeriousM

Hi @ctusch, I'll have a look at it. Thanks for reporting!

@SeriousM

uhm, ähm... @MrCircuit, may you help with this please?

@SeriousM

Thats even easier! Either with GetLocalizedValue (Static method) or with ResolveLocalizedValue (Instance method). Just pick the right overload of t…