VoodooShield/Cyberlock

Very cool, thank you!

 

No problem, hope that helps

 

So then I can't help testing... Do you want to know the specs of my laptop where VS freezes?

 

It may or may not be a hardware issue or software issue. it might help to list our hardware or even just what manufacturer it is.

is this a Dell only issue?

 

Salutations/Greetings!

VoodooShield latest 3.33 Beta is working well on all my PC's. With Windows 10 Anniversary Edition install.
Smooth and nice! Let us know when the next beta version is ready, please?

Kind regards,

 

Moose the freeze issue does not happen all the time but for me it only when my machine has been at sleep for a few hours and then not always. like I said it is a ghost. it might even be some kind of software update issue. nobody know for sure right now. at current we are leaning more to some sort of memory corruption.

 

I've had no freeze issues with 3.33 beta since its introduction..In fact I've never had any freeze issues with any VS release....It must be a software\hardware conflict and a commonality issue that others have.

 

@VoodooShield

Hi Dan

I had VS freeze this morning on my laptop (3rd gen i7, Win 8.1 Ent.) after it had been left on overnight. This is on version 3.33beta running in Smart mode.

Right clicking on the desktop icon brought up the application menu, but it was completely unresponsive, and wouldnt even close. Strangely, though, left clicking the system tray icon actually toggled VS off and on (as indicated by the desktop icon changing accordingly) which indicated the front-end was not completely inoperabale.

I checked Task Manager and the voodooshield.exe process was using over 500MB of private working set memory! - normally this would be about 40MB. Using VMMAP I established this was mostly allocated to Managed heap (not sure what that is?).



While investigating the freeze I opened Process Explorer and immediately received a popup from VS asking me to allow the process to run. This surprised me, as I had always assumed that when VS froze it was not operational and the whole of it's GUI was frozen too. But in this (isolated?) case, VS was popping up, allowing me to block and allow processes as it would normally.

After about 20 minutes the memory usage dropped to about 120MB but did not drop any further after that. I left it another 10 minutes before ending the voodooshield process and restarting VS.

Not sure if it's of any use to you, but at the time of the freeze, I used Procdump to produce a complete memory dump of the voodooshield process. It's over 500MB but will probably compress down to a reasonable size.

I hope some of this information is of help to you.

Mark

 

Dan, for the first time ever the SBS version of VS froze on me today, after an update to Dropbox. I've kept the logs if you want them.

UPDATE: It's just frozen again while updating a large PowerPoint presentation that wanted some MS services to run, this time crashing PowerPoint. Coincidence?

 

Yes - correct Dan

 

I can't really say where is the problem but since moving to 3.08 I didn't have any single problem/ freeze. I can't go with older version as I have only WIN10 available.

 

@boredog,

Post: #12107

understand and appreciate you sharing.

Kind regards,

 

from what mark reports, maybe the freeze is just the gui and not the service?

 

My laptop is an Acer Aspire VN7-791G-576X with the following specs according to Speccy:

 

After the latest update for Win 10 AU (KB3176934) I had no more freezes with VS 3.33 (smart mode).

 

Thank you, but we probably do not need hardware specs anymore. I narrowed down the memory leak and Vlad is going to fix it in a few days when he returns from vacation, so hopefully that will fix the freeze issue completely.

BTW, I have been asked a few times if VS blocks rundll32.exe... yes, VS does block rundll32.exe, but not if the command line came from a whitelisted app in the Program Files (Windows protected) folder. It is perfectly safe and a lot more user friendly then needlessly blocking command lines that should not be blocked.

Run the following command and you will see! Thank you!

Rundll32 Shell32.dll,SHHelpShortcuts_RunDLL PrintersFolder

 

I do not think it is a Dell issue... it should be completely fixed in a few days though, thank you!

 

Great to hear, thank you! We should have the next version by Friday!

 

Great to hear, thank you!

 

Thank you Mark... yeah, that is exactly what is going on... yeah, VS will continue to block even when the gui freezes, and actually it will usually correct itself after the next block and unfreeze. But either way, we need to fix it .

 

Thank you, I think we are good for now, there is no reason to send the logs at this point.

 

I am going to skip the last few posts that refer to the freeze issue... there is no reason to be redundant. We are getting really close, thank you for your help!

 

That would be the best news ever Thanks for your hard work and great support.

 

Great to hear. The only question is and when you find the issue please let us know what the cause is as some like me never had theses freezing issues so if it was .NET or whatever cause and outcome please let us know.

Thanks,

Daniel

 

Vlad is still going to look at a couple of things when he returns from vacation, but there is a chance that the freeze issue is fixed in this version.

Also, please keep an eye on the VoodooShield.exe memory utilization in the task manager… hopefully it will not go sky high anymore.

Please try it and let me know, thank you!

https://voodooshield.com/Download/beta3/InstallVoodooShield.exe