todbot / Blink1Control2

Blink1Control GUI to control blink(1) USB RGB LED devices.
http://blink1.thingm.com/
Apache License 2.0
154 stars 26 forks source link

Blink1Control2 freezing or non-responsive. Version 2.2.7 and 2.2.9. Multiple OS #176

Open mktechguy opened 1 year ago

mktechguy commented 1 year ago

Greetings. I have been testing this for a solution to monitor a MS O365 email address, and light up when 1 or more unread emails are present. I'm testing a low-end HTPC, with Windows and Ubuntu and a high-end custom PC with Windows. All of which after several days of running, the program will stop responding. The HTPC will freeze more frequently, within a day or two, and the Custom PC will last for about a week before freezing. I switched from Windows to Ubuntu on the HTPC because I thought Windows was being too resource heavy and perhaps causing the freezing, and because most of your programming revolves around Linux (I'm fairly green at Linux still).

Systems are: HTPC (BeeLink T4 Mini PC) CPU: Intel Atom x5-Z8500 RAM: 4GB SSD: 64GB eMMC OS: Windows 10 Pro (1607) 64-bit (originally) OS: Ubuntu 20.04.4 LTS 64-bit (currently)

Custom PC CPU: AMD Ryzen 5 5600X RAM: 32GB SSD: 1TB M.2 OS: Windows 10 Pro (21H2) 64-bit (currently)

Blink1Control2 version: 2.2.7 and 2.2.9 used with all systems.

I can't seem to find any log files or event viewer entries to explain why the Blink1Control2 becomes non-responsive. With the HTPC, I noticed that it was using 2.7GB of RAM when it was locking up the Windows OS as well. Force killing the process or rebooting was the only solution. The HTPC with Ubuntu will give an error, which I should have written down more precisely... but to paraphrase it 'the blink app became non-responsive and the system did not have enough memory to submit an error report'

With my Custom PC, it simply stopped working after a week of working well. I could not open controls but still running in the system tray, and was using very minimal resources, like 143MB or RAM etc.

Sorry for not getting more specific information beforehand. If I could get the same email monitoring function from the smaller tools, then that may be my solution as well, if they don't lock up.

todbot commented 1 year ago

Thanks for the detailed description. I'm currently researching a problem with the IMAP event source and that may be the cause of the problem. I assume you've got some email event sources set up?

mktechguy commented 1 year ago

Yes, I've manually setup the mail rule on each computer, no config copies, just first-hand setups. I'm using my work email with Exchange Online (Office365) as the tester. Though currently I've found, as of this morning (July 21st), O365 IMAP is not working with my helpdesk, or the Blink app. I've discovered there is an active MS O365 issue happening with my account regarding Exchange Online IMAP4 Basic Authentication (which will be disabled by Microsoft Oct.2022 anyway).

I've deleted the DEMO events from the list, and created a new rule for mail names "new mail rule 1" The settings are:

server: smtp.office365.com user: "my email" password: "my tested working password" Port: 993 SSL Enabled Play pattern when unread email count >= 1 Pattern: new pattern 0 (modified to blink indefinitely instead of the default 3x) Turn blink(1) off when no match: CHECKED