Application Display is blank

[raentzmi]

When running the display operates as intended. If I leave it running overnight and come back to the display it is blank - completely clear - I will do this again tonight and provide a screen shot of the display and the files listed below.

I restarted the application to rule out configuration or MQTT issue.

Fault bucket 1369497028606575576, type 5
Event Name: RADAR_PRE_LEAK_64
Response: Not available
Cab Id: 0

Problem signature:
P1: MQTT Explorer.exe
P2: 0.4.0.0
P3: 10.0.19044.2.0.0
P4:
P5:
P6:
P7:
P8:
P9:
P10:

Attached files:
\?\C:\Users\XXX\AppData\Local\Temp\RDR99FD.tmp\empty.txt
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER99FE.tmp.WERInternalMetadata.xml
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9A0F.tmp.xml
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9A38.tmp.csv
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9A78.tmp.txt

These files may be available here:

Analysis symbol:
Rechecking for solution: 0
Report Id: a75d84df-408f-446a-8500-58051c029b43
Report Status: 268435456
Hashed bucket: 22f1f2c66f645562a3016e4aa70c43d8
Cab Guid: 0

[hsaturn]

I've ran several time Mqtt-Explorer during a lot more than 24 hours without any problem. Even with about 6/7 graphs.

You did not mention what OS you are using. Maybe you went out of RAM
(I'm not the author nor contributor of Mqtt-Explorer)

[ilgrank]

I can confirm that I too used MQTTExplorer for weeks (Windows 10) without any issue

[raentzmi]

Thanks for the quick response. The OS is Windows 10 Intel i9 with 64GB ram - the Event name points to a memory leak - this is a windows leak detection - I am not saying that there is a leak just that the event subsystem implies it. I have 10 trends all but 2 are at 30 second update and the remaining 2 are at 5 second update. The issue has not happened - since I logged the issue. The MQTT broker is Mosquitto on a RPI 3 and is version 1.5.7 - and I need to update it.... If there is something you would like me to document let me know. Fault bucket 1369497028606575576, type 5 Event Name: RADAR_PRE_LEAK_64 Response: Not available Cab Id: 0 Problem signature: P1: MQTT Explorer.exe P2: 0.4.0.0 P3: 10.0.19044.2.0.0

…

On Tue, Mar 28, 2023 at 4:04 PM ilgrank ***@***.***> wrote: I can confirm that I too used MQTTExplorer for weeks (Windows 10) without any issue — Reply to this email directly, view it on GitHub <#715 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AL4TWK722QODWNPK65QUJTTW6NG6XANCNFSM6AAAAAAWHW7URQ> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[ilgrank]

The developer is not visiting this project since years, I doubt you will get any help in that regard.
I have MQTTExplorer 0.4.0 running uninterrupted for weeks, logging more than 200 topics with thousands of values, and using less than 500 mb of RAM.:

[raentzmi]

This tool is quite good and is my go to - when working with MQTT - I get it and appreciate the feedback. The behavior happened again - should look something like this. [image: image.png] But looks like this [image: image.png] Using process hacker we can see that there are 4 threads - all doing nothing [image: image.png] PID 1592 has a significant drop in memory - The CPU utilization is from me running another tool and is not MQTT Explorer. We can just let this be some documentation on what I would say is an anomaly - as I have run this tool for weeks at a time and never have this behavior. Next steps I would say is up to you. Rob Entzminger

…

On Thu, Mar 30, 2023 at 12:49 AM ilgrank ***@***.***> wrote: The developer is not visiting this project since years, I doubt you will get any help in that regard. I have MQTTExplorer 0.4.0 running uninterrupted for weeks, logging more than 200 topics with thousands of values, and using less than 500 mb of RAM. [image: image] <https://user-images.githubusercontent.com/4583412/228741481-f694dd6b-f651-4cd3-b9a7-4494a2f4f0cb.png> — Reply to this email directly, view it on GitHub <#715 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AL4TWK6QG5GYJ6BESR25TIDW6UNG5ANCNFSM6AAAAAAWHW7URQ> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[ilgrank]

I don't know who you refer to when you say

"Next steps I would say is up to you."

as I am regular user as you are. I was just giving you an advice about the fact that most likely you're looking in the wrong direction since no one else is experiencing your issues, AFAIK.

That said, the original developer is not touching this project since years, I'm telling you since maybe you're expecting an answer from him that will likely never come.
Bye

[gujun720]

Hi, @raentzmi

I would invite you to try MQTTX (https://mqttx.app/), an open-source MQTT client.
We provide an elegant desktop application on Win10 with both 32-bit and 64-bit support.

If you encounter any problems with MQTTX, please raise the issue at https://github.com/emqx/MQTTX/issues.

😁