What steps will reproduce the problem? 1. Trace 2. Press clear log 3. Log doesn't clear

What is the expected output? What do you see instead? A clear log

What version of the product are you using? On what operating system? Latest (3.9)

Please provide any additional information below. When I open the flash log in a text editor and try to delete and save, it says there is a sharing violation, i.e. some other app is writing to it/has it open.

I close chrome and I can then clear the flash log.

i.e. Chrome is writing to it so I cannot clear it through Vizzy

FP 11.0.1.153

Happens in FF and IE9 too. The flash on the page retains control of the flash log stopping Vizzy from clearing. If I close all tabs with flash I can clear the flash log.

FP 11.0.1.153

Happens in FF and IE9 too. The flash on the page retains control of the flash log stopping Vizzy from clearing. If I close all tabs with flash I can clear the flash log.

Thanks for reporting that issue. However, I do not have that kind of problems, so it's hard to debug.

Could that be because you launch your browsers with Admin rights, but Vizzy with non-admin rights?

Sometimes Vizzy locks flashlog too, but only for a moment, while it reads content from it. So if you press Clear at that particular time, log won't be cleared, so you have to press Clear for 3 times in a row.

Tried everything but no fix. So changing logger.

Do you want to say, that using other flash loggers solves your problem?

Not very clear sorry. I've tried many fixes, but I cannot get Vizzy to clear the trace as soon as any browser is open and a flash object has traced in the browser session (the flash object doesn't have to be open). Very odd. It just started happening, no upgrade of anything. I'm using an AIR tracer, not very good but give a clear clearable trace. I'll check back for updates and or mystery self fix at another time.

I experienced this symptom briefly today, but it's now working as expected. I'm on Win 7 Enterprise, Flash CS5.5, Vizzy 3.9.1. The problem initially appeared while I only had Flash running (and Vizzy of course). My traces started getting clipped because they were long (dumping a big XML), and then Vizzy stopped clearing the log.

I started Firefox and viewed the same content but Vizzy stopped tracing from Firefox at all. I quit Firefox, quit FLash CS5.5, quit Vizzy, then started Flash and Vizzy again and the problem had disappeared.

this is very likely that exception happens in vizzy and it fails. If would be helpful if you could run vizzy from command prompt java -jar Vizzy.jar and when Vizzy stops working, send me console output.

This would help me a lot.

Trying to delete the log manually, windows says its open in "plugin container for firefox"

flash is opened in a separate process in firefox, called plugincontainer.exe. Check out Troubleshooting page in half of an hour. I will update it.

This happens with Dreamweaver CS5.5 as well. Any solutions? Everytime Dreamweaver is running the log doesn't update, closing Dreamweaver solves it easily. No clue what so ever why Dreamweaver gets a handle on the Vizzy log file every time.

I guess this is because DW has widges, built with flash. They might take precedence on flashlog.txt file so that other applications (like Vizzy) can do nothing about that.

One possible cause that got me anyway: I am using Adobe Flash debug player 11.4.402.278 and Chrome, FF v15 or IE9 on Windows7. I was unable to clear the flashlog from Vizzy while the browser was running. Sysinternals handle.exe showed either chrome.exe, plugin-containter.exe or iexplore.exe had a handle for flashlog.txt. In Vizzy I also had the 'Buffer Trace Output' option ticked in Extra > Options > Trace Output. After I unticked this and refreshed the flash page in the browser I was able to clear the flashlog in Vizzy while the flash was running.