more G-Labs products

Author Topic: Small Issue with stale error message  (Read 869 times)

November 26, 2014, 04:27:23 PM
Read 869 times

mrburns42

  • *
  • Information
  • Newbie
  • Posts: 11
I don't know if the following is a real bug, or perhaps how it is supposed to work.  I am trying to write a Python script.   I kept getting a Runtime error  about "object reference not set to an instance of an object".    I fixed everything that I could think to fix the error.   Then I realized that the error message appears to be stale.  If I restart the script the time stamp of the Runtime.Error does not change.    It would appear that a log is not being cleared when pressing the Restart button.  Perhaps this is desired operation.   Anyway, attached is a screen shot of what I saw after a restart.   You can see that the module status went to running almost a hour after the Runtime.Error.   

Thanks.


There are no comments for this topic. Do you want to be the first?