Using the button's animation effect caused a memory leak

Aberta
  • Algo errado?
#3,282 1 comentário 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
5/5
Tempo estimado
Mais de uma semana
Facilidade para iniciantes
25/100
Tipo de issue
Bug
Clareza
Precisa de esclarecimento
Status de atividade
Estagnada
Stack de tecnologia
csharp
Domínio
desktop, performance

Direção de pesquisa

Comece reproduzindo o relatório da ComputerInfos.txt fornecida e o código do botão mostrado, usando MaterialDesignRaisedButton com IsIndeterminate habilitado enquanto a janela estiver maximizada. Compare o uso de memória entre os loops de animação e os eventos de hover/leave e, em seguida, verifique se alterar o estado da janela não libera mais nem impede o leak relatado.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

bug evaluation required
Bug explanation

[Machine translation, simple proofreading only]

greeting,Today I encountered a memory leak problem in using MaterialDesign, the details of the problem are as follows:
In some runtime environments (see file [ComputerInfos.txt] for computer configuration)(This behavior is not encountered in my development environment),If and only if the window state is maximized (and has not changed to another state),When the IsIndeterminate property of a button with Style="{StaticResource MaterialDesignRaisedButton}" (no other styles tested) is set to true.Each time the animation effect loops, the memory usage will increase by 3~5MB until it crashes or switches the window state.
Hovering and leave from such buttons also results in an increase in memory usage, which is the same as the effect described above.
If you switch the window state to non-maximized before the crash, the abnormally occupied memory will be freed and will not occur even if it is set to maximize again later.
When the memory is exhausted, an error is reported as shown in the [Error message] in the picture.
All Nuget packages used in the program are shown in the picture [NugetList1, 2, 3].

Regarding the video showing this problem, I put it on youtube because it exceeded the upload size limit, please visit the following two links to view it, or contact my email [email protected] and I will send it to you as an attachment.

[中文原文]

大家好，今日在使用[MaterialDesign中遇到了内存泄漏的问题，问题详细情况如下：
在某些运行环境中（计算机配置详见文件[ComputerInfos.txt]）（此现象并未在我的开发环境中遇到），当且仅当窗口状态为最大化时（且未曾更改为其他状态），将Style="{StaticResource MaterialDesignRaisedButton}"的按钮（未测试其他样式）的IsIndeterminate属性设置为true时。动画效果每次循环，内存占用将增加3~5MB,直到崩溃或者切换窗口状态。
鼠标悬浮和离开此类按钮，同样会造成内存占用增加，效果与上述效果一致。
如果在崩溃前将窗口状态切换为非最大化，那么异常占用的内存将会被释放，即使之后再次设置为最大化，这个问题也不会出现。
内存耗尽时，报错如图片[Error message]所示
程序内使用的所有Nuget包如图片[NugetList1、2、3]所示

关于展示此问题的视频，由于超出了上传大小限制，我将其放在了youtube上，请访问以下两个链接来查看，或者联系我的邮箱[email protected]，我将以附件的形式给您发送。

[图、文、视频资料] [Text, pictures, video materials]

Error message
NugetList1
![NugetList2](https://github.com/MaterialDesignInXAML/MaterialDesignInXamlToolkit/assets/84267336/b724b350-c7f7-4e16-a202-1
NugetList3
5e077130230)

ComputerInfos.txt

https://youtube.com/shorts/PT4MLnNCSo4?feature=share
https://youtube.com/shorts/0R7E03ghs_s?feature=share

[部分代码][Part of the code]

    private void RefernceImageSet_1_Btn_Click(object sender, RoutedEventArgs e)
    {
        if (bGetLicense)
        {
            _region.Activate(_ReferenceImage);
            JobSingleton.Instance.NowWindowsNum = 0;

            //ButtonProgressAssist.SetIsIndeterminate(RefernceImageSet_1_Btn, true);
            //ButtonProgressAssist.SetIsIndeterminate(ModelSetting_Btn, false);
            //ButtonProgressAssist.SetIsIndeterminate(RunSet_1_Btn, false);
            //ButtonProgressAssist.SetIsIndeterminate(ParamSet_1_Btn, false);
        }
    }

When I comment out part of the code, the exception takes up memory and disappears, so I presume that it is a problem with MaterialDesign.
当我注释部分代码之后，异常占用内存的情况就消失了，故推断是MaterialDesign的问题。

Version

4.0.0

Linguagem predominante
C#
Estrelas
16.3k
Forks
3.5k
Merge médio
4h 25min
PRs com merge (30d)
4

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de MaterialDesignInXAML/MaterialDesignInXamlToolkit

Todas as issues de MaterialDesignInXAML/MaterialDesignInXamlToolkit

Issues semelhantes

Mais issues de C#

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.