TPD 4 using 100% cpu
AMXSource
Posts: 7
I have had a quick look through the forums about this but couldn't see anything, my applogies if I'm doubling up...
TPD4 has this issue that is really starting to bug me. If you are aconnected to a master for TP file transfers, and the connection is broken (this frequently happens when you transfer the TP file before you transfer the .tkn), TPD4 pops up a little alert to say that the connection has been lost.
Thats nice of it to say so, but it's not so nice when you have a look at the CPU usage while the alert is active. 100%... You probably wouldn't notice too much if you didn't know about it, but my laptop fan starts going crazy and windows get obviously bogged down.
As soon as you click OK on the alert everything goes back to normal.
Anyone else had this issue?
TPD4 has this issue that is really starting to bug me. If you are aconnected to a master for TP file transfers, and the connection is broken (this frequently happens when you transfer the TP file before you transfer the .tkn), TPD4 pops up a little alert to say that the connection has been lost.
Thats nice of it to say so, but it's not so nice when you have a look at the CPU usage while the alert is active. 100%... You probably wouldn't notice too much if you didn't know about it, but my laptop fan starts going crazy and windows get obviously bogged down.
As soon as you click OK on the alert everything goes back to normal.
Anyone else had this issue?
0
Comments
Yes, this is a problem. I sure wish this one would get fixed as it has been around for too long.
but i have to say, since i recently rebuilt my Windows install, and freshly re-installed AMX apps etc, i really have had no unexplained crashes like i used to.
i also haven't added Office and various other bits and pieces i used to have installed.
the only 'explained' crash i've had was when the entire OS crashed to a blue sky, with a report that the ATI video driver caused it. i can understand that as i haven't updated that from it's default install version.
i know this isn't a direct answer to the question, but since i critisized TPD4 when it did crash, and now it doesn't (for me), i thought i better stand up for it
my suggestion, though painful, is a clean windows rebuild, then closely note new installations of applications until TPD4 may crash on you again.
(and it is very painful i know. it tooks day to find everything again, backup/restore data, get serial numbers, start again if things go wrong
i just crashed TPD4 as i went to do an upload over the internet.
just as the transfer percent bars were appearing.
i restarted TPD4 and the transfer went fine (maybe the panel was asleep when i first started [an MVP-8400])
i have to admit the connection to the house is slow.
in answer to the first question though, i checked and the notebook didn't hit 100%, just sat at single digit level.
I have tried to track the exact behavior/sequence of events of 'the TPD4 crashing when downloading' thing before. It seems to most often happen at the moment of attempted connection, however, I have now seen it a number of times at the moment of download...post connection.
So, no distinct pattern that I can determine.
It's sneaky, annoying and unpredictable, however it does teach you pretty quickly to save before connecting!
In relation to the thread topic, I have exactly the same behavior from my cpu when tpd4 reports connection lost.
I had tpd4 open and connected, nsx running, and I downloaded a new code and got the 'connection lost' box warning from tpd4 as expected.
I'm starting to think the word 'lost' is a bit more accurate than just an expression now!
I pulled up task manager and cpu usage was at 100% too.
I (sadly) have to run windows, therefore I need all the cpu I can get....please leave me alone tpd4!
:-)
Why is it people here like to use TPDesign for file transfers and not NetLinx Studio?
Restarting TPD4 each time is just time consuming.
If I am tweaking/testing panel mods, it's very convenient to make a quick change and send it with the Redo Last Transfer button.
Very neat and sweet. No flipping apps, deselecting source code from d/l area, reselecting panel file etc etc.
I agree, especially since it?s so easy enough to duplicate. Open TPD4 and connect to an NI master. Use Netlinx Studio 2 to reboot the master. Bam, TPD4 has a major brain fart which pegs the CPU at 100% and won?t let go until the message box is acknowledged.
When this happens to me, my CPU does not goto 100%, but I will be unable to get/open any type of network connection untill I click OK in TP4. This includes websites/email/and connecting to the master, but once I click OK, everything returns to normal.
Paul
1) Close all programs.
2) Open the task manager and minimize into the system tray.
3) Open TPD4 (maximized) and connect to a master.
4) Open NS2 (maximized) and via the Tools menu, reboot the master.
5) When the reboot starts the task manager CPU icon gets pegged and the tool tip reads CPU Usage 100%. (My laptop fan kicked on soon afterwards also as AMXSource noted.)
6) Double click the task manager icon to bring up the task manager and select the Processes tab.
7) Sort by CPU usage and TPD4 will be at the top of the list and should be somewhere around 98% and will stay that way until step 8.
8) Switch over to TPD4 and acknowledge the Connection Lost message box. As soon as the message box is acknowledged, CPU usage for TPD4 will drop to 0%.
I get the same exact results every single time for each OS. Mileage may vary on the CPU usage by a few percent.
The pegging of the CPU only happens with the combination of TPD4 and NS2. If I connect to the master with TPD4 and pull the network jack from the NI-700 or if I yank power from the NI-700, then TPD4 will still throw the message box up after a few seconds as expected but it won?t grab the CPU by the throat.
Also, if you insert the following step:
3A) Minimize TPD4.
Then I believe the jumbled tool bar scenario that has been mentioned several times on the forum will happen after the CPU gets pegged and you switch over to TPD4.
I have found that this scrambling of the toolbars only occurs if TPD4 is minimised at the time of disconnection.
If you leave it maximised and switch to nsx via the task bar, then download your code, you will only see the disconnection issue spoken about, not the toolbar carnage.
Until then, disconnect after a transfer (sure would be nice to have an option to do this) to save your PC from running away like WOPR did in WarGames and to keep you toolbars in tact.
It has been a well known fault for at least 18 months that I know about...