1 Topic by softtouch

  • softtouch
  • Member
  • Offline
  • Registered: 2010-06-01
  • Posts: 12

Topic: When killink app in taskmanager, log is not readable anymore

I write the .sil to file, buffer is 1024.
When killing my app in taskmanager, the .sil is not readable and has always a size of below 100 bytes (64 bytes or 20 bytes usually).
When trying to read it, I get "stream read error".
The problem is, the whole logging is useless when the .sil is not readable when the app has to be terminated. Any way around this?

2 Reply by tgurock

  • tgurock
  • Administrator
  • Offline
  • Registered: 2009-07-09
  • Posts: 628

Re: When killink app in taskmanager, log is not readable anymore

Hello,

Could you send us such an example log file to contact@gurock.com? The log shouldn't be unreadable, of course, the only thing that can happen when you are killing your application via the task manager is that the log messages in the buffer aren't written to the log.

Regards,
Tobias

3 Reply by softtouch

  • softtouch
  • Member
  • Offline
  • Registered: 2010-06-01
  • Posts: 12

Re: When killink app in taskmanager, log is not readable anymore

Sent log by email. Thanks.

4 Reply by tgurock

  • tgurock
  • Administrator
  • Offline
  • Registered: 2009-07-09
  • Posts: 628

Re: When killink app in taskmanager, log is not readable anymore

Thanks for the log file. The reason for this error message is that the Console does not correctly handle empty encrypted log files as I just found out. The 20 bytes are for the file header and some additional encrypted related data. Since you are using an I/O buffer and kill your application before the data is flushed, no log data is written and the log file is basically empty.

The Console does not handle this situation correctly. It doesn't influence the stability or state of the Console but the error message shouldn't be displayed, of course. The correct behavior would be to load the log file as usual and to not display any log messages (since the log file is empty). A fix for this will be included in the next SmartInspect version.

This would explain the behavior for the 20 bytes log file. If you also have additional log files with other sizes that generate the same error message in the Console, it would be great if you could send them to us as well.

Thanks,
Tobias