Here is mine. @Inoki Do you use Bittorrent at all? Can you try switching out of “Ask to connect” and disable webcam/mic blocking and see if it makes any difference? I am using “Ask to connect” myself with this memory usage.
I have GlassWire history going back since the early summer myself and memory usage has been low for me, but I don’t use Bittorrent.
I use Bittorrent, but occassionally. When I measured that it wasn’t running. Right now MEM usage is 235 MB and I haven’t started Bittorrent in a while.
I restarted my computer and MEM usage went down but it goes up probably because of extended run times without reboots and shutdowns.
I don’t want to turn off Ask To Connect since it’s the main reason I paid for the software.
Bittorrent accesses tons of hosts simultaneously, so it uses a lot of memory for GlassWire to catch up. You can clear some of your history to get the memory back down lower if you think the memory usage is too high.
You can also switch to “incognito” mode when using Bittorrent to help.
I also use “Ask to connect” myself all the time and I don’t see much of a memory increase for it. We’re working on making changes to that mode that decreases memory usage even more.
1.2.73 version Glasswire Basic is using 1.5 GB of my memory. This absolutely make it unusable for me. I’m running Autopano Giga image stitcher and it only uses 2GB for a humongus panorama. This is ridiculous. If it cannot be fixed I would like my money back for a useless product. I just purchased a few days ago and I didn’t notice the free version using this much memory. Is there any chance of getting a refund? PLEASE
Please uninstall GlassWire, reboot, then reinstall our latest version with the “clean” option and let us know if it solves the problem.
Ken I did as you suggested, uninstalled, rebooted and installed the latest version with the clean option. I attached a jpg with a collage of info. After 20 minutes of running it was up to 1703576 MB as you can see. The screen shots of my task manager were only a few minutes apart. It was eating ram actively as you watched it and running 13% on the CPU. When I tried to shut it down, I got a BOD when ending the GWCtlSrv.exe and it said there an exception in gwdrv.sys
Dont know what’s up but it isn’t going to work on my system as it currently exists. I see from the forum that this has been ongoing for quite a while so I don’t expect anything substantial to change soon. If you could refund my purchase I will consider you again if you get it working properly. The screenshot of GW here shows how it quit running the graph but the memory was continuing to be eaten.
Regards,
I see your graph is blank, so if your graph is blank you shouldn’t be using much memory at all. The only thing I can think of is that your PC is somehow communicating with such a large number of hosts simultaneously it’s causing GlassWire to be unable to write them all and it’s maxing it out.
I don’t see Bittorrent. Have you run a Malwarebytes scan lately after updating it to make sure you don’t have some kind of malware infection? Are you running some type of server from your PC?
What OS version are you using? We will try to reproduce this on our end.
I found a program (Autopano Giga) that was blocked in the GW firewall but was apparently trying to phone home repeatedly to check for updates. Once I let that program through the firewall the problem seemed to stop. GW is now using 40k to 90k bytes with no CPU cycles showing in Task Manager. You may want to take a look at why such a thing would be happening. It seems to defeat the purpose of a firewall if it can be brought down by repeated requests for connection. In addition GW did not give any indication of the problem other than its runaway behavior. I will keep you informed of how things go from here. Thanks for your quick replies. You can download a trial of that software btw if you want to test it out. Once I let it through all my firewalls the problems stopped
Yes, you’re right that blocking a program should not use more memory or resources. We will try to find that program and see if we can recreate this problem. Nobody has ever reported something like this before so I’m not sure how it’s possible.
Were you in “Ask to connect” mode, or “Click to block” mode?
Ask to connect. I am also running another firewall called windows 10 firewall control at the same time. You can get a demo of that also.
It was possible on my machine!
Windows 10 firewall control reported that Autopano tried to connect millions of times after I looked at the history.
Thanks again
Running version 1.2.100. Memory usage just keep ramping up until there is no more, all in a matter of minutes. Much as I hate to do it, I have to uninstall this puppy. Let me know when it is properly house-broken.
As you can see above with Moxaman, there ended up being an application that was making millions of outgoing connections. High memory usage with GlassWire can indicate malware or unusual network activity on your PC. You may want to look closer at GlassWire to see what’s so unusual on your PC’s network behavior that GlassWire would need so much memory.
You may also want to scan your computer for malware/viruses.
I scanned for malware and found none. I looked closely for undue network traffic, and found none. I do think it curious that it found some BACnet traffic, which I could not find with WireShark.
Maybe you need to add a configuration parameter to let the user set a limit to the memory that is allocated.
For most people GlassWire does not use excessive memory. We are making an option on an update that allows users to use very minimal memory, but the update is not finished yet. It will be a free upgrade for everyone.
OK, let’s try to figure out why it has a problem on my machine. The machine is about 10 years old, with an AMD processor, 4GB RAM, a graphics card, and running Win7 Ultimate. The Windoze firewall is disabled, and I’m running the (latest) free version of Glasswire with no config changes (such as things to block in the built-in firewall). This machine generally has very little network traffic to the outside world, but it does export a couple SMB disks, and import 4 or 5 NFS disks. Network traffic happens mostly either in a browser or when accessing one of those disks. When I turn the machine on, glasswire sucks up RAM at a rate of something like 100MB/minute until there is no more, even with no (explicit) networked disk I/O or browser activity. The “background” network rate (mostly to support those networked disks) is about 5Mbit/second on my GB ethernet. It’s a fair number of packets, but in the absence of explicit disk I/O, they’re small. My Bittorrent is running on another machine.
I’m a bit worried that your update “that allows users to use very minimal memory” will result in an unusably slow program.
Please try a clean install GlassWire using our “clean” install option, then try using the software with your disks disabled. We will then know if the traffic from the disks is causing the problem or not.
I don’t use disks like that myself currently, so maybe it’s that?
OK, I’ve installed the latest version clean. Memory usage is less than 39MB, and all is well with the world. Then I mount one of the exported disks from this laptop running Linux. After a while the network traffic starts up, and memory usage starts ramping up at a rate of about 1MB/sec. Note that I haven’t actually accessed the disks.
When I unmount the disk, network usage drops to nearly nothing, but the 1.5GB RAM for GWCtlSrv is only marginally reduced. Half an hour after the unmount it is still writing to the disk at a rate of over 2MB/sec.
I also mount these SMB disks from two other unix machines, but it appears that these machines are running an older version of Samba. These other machines do not caused this increased network traffic.
So anyway, you now have a way to test this for yourself. Access a Windoze disk from a machine running the latest version of Samba. I don’t know if the machine has to be unix or not.
By the way, here’s a couple suggestions:
On the Usage tab, I can’t figure out which colors resprsent what.
It would be nice if you it were possible to see packet count as well as byte count.
On uninstallation, the service should also be terminated.
Thank you for your detailed report and feedback. We plan to improve Usage soon.
I’m pretty sure our service is quit on uninstall. I will try to recreate this on my machine. Sorry for the problem.
Looking into it further, it seems that the traffic was on the order of a few thousand (small) packets per second, so it is unsurprising that glasswire had difficulties handling it. This traffic was due to a misconfiguration on my Linux laptop which has now been solved. So I guess I have to thank you for helping to find this problem.
