Home› AMX User Forum› NetLinx Studio

NS 2.5.0.163 Causing Hihg CPU Usage after Shutdown

TurnipTruckTurnipTruck Posts: 1,485
in NetLinx Studio
Greetings,

I have been noticing that after opening, using, then closing Studio that my PCs CPU usage will hang around 60% until I reboot the PC. Before starting studio, usage is close to zero, as expected.

PC is a P4 running XP SP2, with a fresh Windows install.

Any similar experiences or suggestions?

Thank you.

Comments

  • matt95gsrmatt95gsr Posts: 165
    I've been having the same trouble for the last few days, and have been trying to pinpoint it myself. Problem is, I haven't had too much time to test and try to narrow it down to a specific app. However, I suspect that you may be onto something as I just reinstalled over the holiday weekend and didn't seem to have the trouble until I reinstalled all of my AMX apps and started to try to get some work done. I'll keep poking at it and see if I can narrow it down to NS2. The machine is an AMD Athlon also with a fresh XPSP2 install and NS 2.5.0.163.
  • DarksideDarkside Posts: 345
    I just launched and closed the NSX app a few times but no symptoms like you.

    I haven't tested this theory..but...

    ..is it related to the disconnection issue we KNOW exists with TPD4? ...that is if the connection to the master you have with TPD4 is terminated by, say, a reboot, your pc processor will spin at 100% until you remove the little box in TPD4 that alerts you to the disconnection.

    Perhaps something of a similar nature in NSX?

    Just a thought - might try some stuff later
  • TurnipTruckTurnipTruck Posts: 1,485
    Closing anything and everything AMX-related still leaves my CPU usage at around 50%. The only way to get it back to zero is to reboot the PC.
  • DHawthorneDHawthorne Posts: 4,584
    I haven't seen this particular problem, but I tend to suspect it's comm related too. On a hunch, have you tried stopping all communications before closing it?
  • TurnipTruckTurnipTruck Posts: 1,485
    DHawthorne wrote:
    I haven't seen this particular problem, but I tend to suspect it's comm related too. On a hunch, have you tried stopping all communications before closing it?

    Not specifically. But I will make sure to close all comm next time. Good idea.
  • DHawthorneDHawthorne Posts: 4,584
    TurnipTruck wrote:
    Not specifically. But I will make sure to close all comm next time. Good idea.

    Don't just close all the windows that initiate communications, use the button under Settings that stops it dead. Sometimes Studio leaves things running.
Sign In or Register to comment.