NetSetMan Support

PeterL

Member

Registered: 2017-01-18

Posts: 4

Access Violation with version 4.3.2

Since Version 4.3.2 my profiles are not working anymore. I always get an error message:
Exception class: EAccessViolation
Exception message: Access violation at address 00446F0B in module 'netsetman.exe'. Read of address 00000008

NetSetMan Support

Administrator

Registered: 2005-08-06

Posts: 1,878

Re: Access Violation with version 4.3.2

We've fixed this error already. Please update to version 4.3.3!

turtle fan

Member

Registered: 2017-10-24

Posts: 2

Re: Access Violation with version 4.3.2

FYI, I am getting the Access Violation error now with v4.5.1. Specifically, the error box appears when I hover over the Netstatman tray icon. It works fine for a while, after reboot, and then I notice the auto-switch not working and start getting the error.

I found that it also resolves by simply closing and restarting the NSM process, so it is really just an annoyance, and this post is just FYI.

Acer Aspire Laptop 7741
Windows 7 64 Home Premium
DEP setting (default)
Comodo ISP 10
Atheros AR5B97

NetSetMan Support

Administrator

Registered: 2005-08-06

Posts: 1,878

Re: Access Violation with version 4.3.2

Can you reproduce the problem reliably? If so, we would provide you with a special debug version allowing to create a detailed log. Hopefully, these details will help us to determine the cause of the problem.

turtle fan

Member

Registered: 2017-10-24

Posts: 2

Re: Access Violation with version 4.3.2

No, I cannot reproduce it at will, and as a developer myself I know that will make debugging much more difficult. It does "always" happen at some point, but not at a predictible time. Would it be practical to run the debug version indefinitely and hope to log the error whemever it occurs?

In the meantime, I will also look at the system logs when I have a chance, but not much time between my work/school schedule.

NetSetMan Support

Administrator

Registered: 2005-08-06

Posts: 1,878

Re: Access Violation with version 4.3.2

Would it be practical to run the debug version indefinitely and hope to log the error whemever it occurs?

Yes, definitely. We'll prepare the debug version and send it to you soon.