What could make the threads window stop working?

Follow

Kelly Painter

• August 21, 2009 18:15

I have CWARM 2.0.3 and the Threads window was working fine.  I rebooted and now it doesn't.  I press "Reload Script" and nothing happens.  I imported Threads.js into my project so that I could edit the count loop to look for 20 processes rather than the default 10.  I did that a long time ago and it has been working fine.  Otherwise, I can't think of anything I have done that would cause the Threads window to suddenly stop functioning.

Could it be possible that our IT people pushed something out the interferes with CWARM javascript engine?  The reason I suspect that is when I reboot, that is when they shove out their "surprises" then.

 

0

• 

  Kelly Painter

  • August 21, 2009 18:51

  My co-worker reports that his CWARM v2 Threads window also suddenly doesn't work.  Leads me to believe it is an IT created "feature".

  0

  Comment actions Permalink
• 

  Paul Curtis

  • August 21, 2009 19:33

  Can you make sure the file name is *exactly* "threads.js" to the letter with that capitaliztion?

  0

  Comment actions Permalink
• 

  Paul Curtis

  • August 21, 2009 19:34

  Oh, the JavaScript interpreter was something I wrote so isn't affected by other updates to the OS.  Unless there is something anti-viral going on and threads.js becomes inaccessible.

  0

  Comment actions Permalink
• 

  Kelly Painter

  • August 21, 2009 20:21

  1. Yes, the file is "threads.js" exactly.  It has not changed since June 6th.  It was working this morning prior to a reboot.

  2.  Anti-viral - yeah...We have that Symantec Endpoint Protection.  I suspect that an update to that piece of crap is responsible.

  0

  Comment actions Permalink
• 

  Paul Curtis

  • August 21, 2009 20:42

  You should be able to debug this using rudimentary changes.

  Threads.js provides a set of functions but the one that's called by the IDE is called update().

  Change Threads.js's update()  to be:

  function update()
  {
    Threads.clear();
    Threads.add("TEST", 0, "", []);
  }

  You can rename old old function to something other than update() for the time being.

  When you now reload the script, do you get anything in the Threads window or is it still empty?

  0

  Comment actions Permalink
• 

  Kelly Painter

  • August 21, 2009 20:58

  Unfortunately, still blank.  I suspect that Endpoint doesn't like crossscript.exe trying to open .js files.  I bet they have marked .js files as "unsafe".

  0

  Comment actions Permalink
• 

  Kelly Painter

  • August 24, 2009 14:07

  Endpoint must have been the problem.  I complained to our IT people about this problem.  Today, I see that the Threads window is working again.  There was another application that had some issues and today, it is back to normal as well.

  0

  Comment actions Permalink
• 

  Kelly Painter

  • August 27, 2009 00:19

  Well, this is strange.  Sometimes the Threads window works and sometimes it doesn't.  I am not really sure what is going on with it.

  0

  Comment actions Permalink

Please sign in to leave a comment.