We had a major storm through here recently and we suffered damage to the house roof and ceilings. I just received the quote to repair. I’m hoping that a small fraction of the 80,000 odd people that download SDIO and/or Desktop Info every month won’t mind chipping in a few dollars to help out. Click on the big blue button at the bottom of the page to help us keep a roof over our heads, literally!
Guests have read-only access to our forums. If you wish to participate you will need to register. Be sure to activate your account from the email sent to you when you register.
Greetings Glenn:
Back here because i am facing the issue I posted about some months back. I updated to version 3.20.1.4935, but still experience freezing of the application
Here are some details:
1. Screenshot of the moment in time, when the application froze, and the date today (system clock)
2. Relevant portion of the log file. Last entry is at the bottom
I haven't seen anyone else with this issue. Is there something unique to me that's causing this? I noticed this usually happens before/after resume from sleep/hibernation.
Please advise
7/14/2025 12:18:52:562 ERROR STACK DUMP 7/14/2025 12:18:52:391 DEBUG [ProcessData] networkinterfaces 7/14/2025 12:18:52:391 DEBUG [AddDisplayLines] 7/14/2025 12:18:52:393 DATA [ProcessData] networkinterfaces Ethernet IP 169.254.110.146 Mask 255.255.0.0 GW <null> 7/14/2025 12:18:52:393 DEBUG [AddDisplayLines] 7/14/2025 12:18:52:393 DEBUG [AddDisplayLines] 7/14/2025 12:18:52:393 DEBUG [AddDisplayLines] 7/14/2025 12:18:52:393 DEBUG [AddDisplayLines] 7/14/2025 12:18:52:395 DATA [ProcessData] networkinterfaces Loopback Pseudo-Interface 1 IP 127.0.0.1 Mask 255.0.0.0 GW <null> 7/14/2025 12:18:52:395 DEBUG [AddDisplayLines] 7/14/2025 12:18:52:411 DEBUG [AddDisplayLines] 7/14/2025 12:18:52:461 DEBUG [AddDisplayLines] 7/14/2025 12:18:52:477 DEBUG [SetUserVariables] Ethernet IP 169.254.110.146 Mask 255.255.0.0 GW <null>|Loopback Pseudo-Interface 1 IP 127.0.0.1 Mask 255.0.0.0 GW <null> 7/14/2025 12:18:52:489 DEBUG [SetAlarms2] networkinterfaces 0 7/14/2025 12:18:52:508 DEBUG [TConfigItem.UpdateChartData] 7/14/2025 12:18:52:545 DEBUG [DoProc] 7/14/2025 12:18:52:545 DEBUG [GetHttpGet] http://my.ip.fi 7/14/2025 12:18:52:545 DEBUG [SetDataArray] 7/14/2025 12:18:52:549 DEBUG [SetStringArray] 7/14/2025 12:18:52:549 DEBUG [GetUrlContent] url= http://my.ip.fi, timeout=3000 7/14/2025 12:18:52:560 ERROR [GetHttpGet] [e:EIdSocketError Socket Error # 11001 Host not found.] 7/14/2025 12:18:52:590 ERROR STACK DUMP 7/14/2025 12:18:52:579 TIMING [TCollector.GetItemData] uid:httpget - (time: 16ms) 7/14/2025 12:18:52:584 DEBUG [ProcessData] httpget 7/14/2025 12:18:52:588 ERROR [ProcessData] httpget : Socket Error # 11001 Host not found.
i see 2 httpgets, both failed gracefully due to network outage. what happens in the config after that?
i see 2 httpgets, both failed gracefully due to network outage. what happens in the config after that?
Unfortunately, the log does not record anything after that.
ini file.
ini file.
Here it is.
[options]
top=0
right=10
width=585
font-face=Arial
font-size=10
log=%appdata%\DesktopInfo\desktopinfo.log
log-level=debugonerror
[screen-saver]
font-size=22
width=1005
formcolor=501020
font-face=Arial
centerv=1
centerh=1
[options-w]
top=100
centerh=1
width=870
font-face=Arial
font-size=10
formcolor=501020
log=%appdata%\DesktopInfo\desktopinfo.log
log-level=debugonerror
[text]
noresults=<n/a>
error=[error]
null-result=<null>
unknown=Unknown
executing=<executing>
menu-ini=Select Config
menu-export=Export
menu-snapshot=Snapshot
menu-reload=Reload
menu-configuration=Edit Configuration
menu-log=Open Log File
menu-manual=Read Manual
menu-wmode=Start W Mode
menu-about=About Desktop Info
menu-quit=Quit
nav-previous=Previous Page
nav-home=Home Page
nav-next=Next Page
[items]
DATETIME=interval:2, x:%center-h%, y:0, align:c, style:b, font-size:120%,display:%long_date% %10
BOOTTIME=display:%9 %10
CPU=chart:line max:100 series1:1 color1:00ff00 series2:2 color2:bb00bb,alarms:(%1 ge 80 0000ff)(%2 ge 40 0000ff),display:Tot: %1[2.0f]%\, Krnl: %2[2.0f]%\, Q: %3
TOPPROCESSCPU=font-size:80%,text:Top Cpu,display:%1 (pid:%2) %3[1.1f]%
COMMENT=font-size:50%
PHYSICALRAM=font-size:120%,color:b0ffb0,alarms:(%3 ge 80 0000FF),display:%1[3.1b]B / %2[3.1b]B
TOPPROCESSMEM=font-size:80%,color:b0ffb0,counter:pu,text:Top Memory,display:%1 (pid:%2) %3[1.1b]B
PAGEFAULTS=color:b0ffb0,font-size:100%,alarms:(%5 le 80 2222e0),display:Tot: %1[1.0f]\, Hrd: %2[1.0f]\, Hit: %5[1.0f]%
COMMENT=font-size:50%
NETWORKPERF=row-text:%instance%, \
chart:line scale:log row-id:%instance% series1:%BytesReceivedPersec% color1:00ff00 series2:%BytesSentPersec% height:2 color2:bb00bb,\
alarms:(%BytesReceivedPersec% ge {{%CurrentBandwidth%/8*95/100}} 2222ee)(%BytesSentPersec% ge {{%CurrentBandwidth%/8*95/100}} 0000ff),\
display:R: %BytesReceivedPersec%[3.1b]Bps\, S: %BytesSentPersec%[3.1b]Bps\, B: %CurrentBandwidth%[1.0B]bps
NETWORKINTERFACES=operstatus:1,display:%2 IP %8 Mask %9 GW %17,friendlyfilter:-virtual-Adapter
HTTPGET=interval:1800,source: http://my.ip.fi,text:Outside Global
NETWORKINTERFACES=operstatus:1,display:%2 IPv6 %26 GW %18,include-temp:1,friendlyfilter:-virtual-Adapter
COMMENT=font-size:51%
LOGICALDRIVES=diskio:1,font-size:85%,chart:bar max:100 series1:7 threshold:75,alarms:(%11 ge 10000000 0000f0)(%13 ge 10000000 0060f0),row-text:Drive %1:%3|(%2),display:%6[1.0B]B / %5[1.0B]B|%chart%| r: %11[1.1B]B/s\, w: %13[1.1B]B/s\, q: %17
WMI=interval:60,text:Anti-Virus,namespace:root\SecurityCenter2,query:AntiVirusProduct,display:%displayName% %productState%[bit:4096:Enabled:Disabled] and %productState%[bit:393216:up to date:not up to date]
LOG=interval:60,text:Desktop info - %var1%
ok just the one httpget. after that there is networkinterfaces, logicaldrives, wmi and log items.
the question is whether the application has locked up and stopped responding or whether the collector has stopped collecting. It looks like the latter. The difference is the application itself is still responsive, you are able to navigate pages, right click context menu etc is still working, but it is no longer collecting data.
i'm putting my money on the wmi item. if wmi does it's trick of blocking for an indeterminate period of time that will result in what we see here. In my experience, WMI blocks for about 2 minutes and then carries on as if nothing happened. However the exact time will vary depending on the machine's memory configuration.
If this is the case you can solve the immediate problem by running wmi items in a thread. This will allow the collector to continue working while wmi is twiddling it's thumbs. However, if wmi is your problem then all wmi actions, in this program and every other application will be blocked until wmi deigns to continue.
@glenn If I right-click and select "reload", the application disappears from the desktop. it seems I have to launch a new instance. I will try and take out the wmi section and see if it helps.
Unfortunately the no-wait parameter did not seem to solve the issue. I still do need the AV status, so if there's any way I can get that outside of WMI, that would be of great help. Thanks.
@uhondo looks like it's in the registry: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Security Center\Provider\Av
While testing if we could get it using REG2 I found a bug reading the integer. That will be fixed in the next release.
