Shoutbox

I can't reproduce this problem like you told it. Opening logs of the same chat you're chatting in goes fine and it updates (after pressing on the refresh button of course) like it should. No crashes while that log is opened in the Log Viewer while chatting further.

But there is unfortunatly no temporary file if you use local logging.

The log is opened directly from the file on disk (it is not copied to a temporary file first). The same goes for writing to the log; it is written to directly (not first to a temporary copy and then merged to the existing file).

As for the crash. This is a big bug indeed! And it is sort of crazy that it wasn't found before. As such, I do hope this is fixed ASAP.

Your log file however will mostlikely be lost, unless you can 'revive' it again using tools which search for removed files on disk. Maybe if you're lucky, portions of the log can be found like that.

Another option would be if you had online logging enabled: in that case the log may have been saved to your MyPlus!-account.

And even if it didn't (it failed to upload for some reason), you can maybe find the temporary file (online logging does create a temporary file) in a folder named 'plusTemp' in your TEMP folder of Windows or in the Plus! log directory (depending on how your Windows user account is set up). However, note that this temporary file is encrypted. In order to have the decrypted version you need to close Windows Live Messenger. Messenger Plus! should then tell you that not all log files have been uploaded and should ask you if you want to preserve them to try again later. You should answer yes. The log file will then be decrypted and saved in a subfolder named 'Backup' in your Messenger Plus! log directory.


PS: Also note that due to maintenance on the servers, it can take a while for the Log Viewer to show all the logs (it tries to connect to the server but it can't). During this time it may appear as if the Log Viewer has crashed though because it doesn't react on anything (depending on your internet speed of course). But in reality it is simply trying to connect. After a while it will give up and you would be able to continue viewing the logs.