search

YetAnotherPomodoroApp / YAPA-2

Minimalistic desktop timer app for Pomodoro Technique users
https://yapa2.app/
MIT License
518 stars 57 forks source link

YAPA slows down machine #32

Closed Gennady-G closed 6 years ago

Gennady-G commented 7 years ago

Hi!

It really slows down my laptop. But I need few hours to see it (3-5 intervals for 50 minutes). Think there is a leak, but not sure how to catch it. Maybe I need to install profiler or use tools from Sysinternals? Do You have any idea?

floatas commented 7 years ago

What do you mean by slow down ? Task manager starts to show high CPU\RAM usage ?

floatas commented 7 years ago

In order to catch it, you can open Task Manager find YAPA2 process and create dump file (right click on process). Zip it and attach here.

Gennady-G commented 7 years ago

What do you mean by slow down ?

"Slow down" - it slowly switches between application windows, hangs. If I close YAPA it stops hanging. It occurs after few hours of application work

Task manager starts to show high CPU\RAM usage ?

my RAM usage is high all the time.. I'm not sure it is related with RAM. maybe it is HDD issue?

Will try to create dump net time

Gennady-G commented 7 years ago

Yapa with new colors looks great imho)

2017-10-03_223808

Also right click works much faster. Have you made some improvements in this area?..

I cannot reproduce bug when my pc hangs, so let's close it. And if I have more data or dump I'll reopen/recreate it.

Best regards,
Gennady

Gennady-G commented 6 years ago

Think I catched something.

After few hours of work my PC hanged (mouse moved slowly, youtube hanged, etc). I launced process explorer. Please note "Page Faults" columns(9th from the left). This number (149'829 was permanently growing). Also other numbers I think are too big ("Working set" is slightly less than chrome has. But chrome has ~25 high-loaded tabs and open DevTools, and Yapa is counter. Why too big values?..)

2017-10-25_170354

I created dump, made screenshots and then closed Yapa. After this all started to work very fast again.

What I can say is that Yapa was opened (not minimized). And I also suppose that this behaviour starts after few hours of work. Maybe there is a leak in .NET, or a conflict with another program..

YAPA.exe.txt - Process Explorer log (You need https://docs.microsoft.com/en-us/sysinternals/downloads/process-explorer to import it) YAPA.exe.txt

2017-10-25_170504.zip - screenshots 2017-10-25_170504.zip

The whole dump is too big. Do You nedd it? I will upload later if needed

I can attach logs from here: "C:\Documents and Settings\Administrator\AppData\Local\Application Data\Microsoft\Windows\WER\ReportArchive" ReportArchive.zip

Gennady-G commented 6 years ago

dump: https://mega.nz/#!WkNmCbJa!gDXtsihG6A8tLUdnOuG_DwkkwvFkAKQSbXGj1ChZyWo

floatas commented 6 years ago

Reopening for visibility.