Trace logger for GB core crashes when I switch to file output

[GoogleCodeExporter]

What steps will reproduce the problem?
1.Load ROM
2.Click on Trace logger
3.Switch to File output

What is the expected output? What do you see instead?
Sometimes the emulator crashes with this message.

What version of the product are you using? On what operating system?
1.8.4. Windows 7 64 bit

Please provide any additional information below.
Tried replicating on NES, but didn't happen. 

Original issue reported on code.google.com by YojimboG...@gmail.com on 23 Oct 2014 at 1:06

Attachments:

• Untitled.png

[GoogleCodeExporter]

I couldn't repro, but I came up with a theory.

Looks like we were creating a filestream and leaving it open. In the event that 
the OS hasnt flushed the file creation event by the time we log a line, the 
file wouldn't be there.

In r8102, I changed the code to dispose (force synchronously flush) the file we 
created, so that hopefully it will be there by the time the logging begins.

Whether or not this bug manifested depends on many factors of the system (speed 
of emulation of core, operating system version, disk speed and activity) so it 
may be hard for anyone but you to check.  This is why it only happened in GB 
(thats my theory, anyway)

Original comment by zero...@zeromus.org on 23 Oct 2014 at 5:16

• Added labels: ****
• Removed labels: ****

[GoogleCodeExporter]

Since we have a supposed solution, closing.  Reopen if it's reproducible after 
change.

Original comment by goyu...@gmail.com on 20 Nov 2014 at 4:07

• Changed state: Fixed
• Added labels: ****
• Removed labels: ****