ir73 / flash-tracer

Automatically exported from code.google.com/p/flash-tracer
0 stars 0 forks source link

Clear Log doen't clear log #27

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
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 

Original issue reported on code.google.com by d...@believecreative.com on 16 Nov 2011 at 4:33

GoogleCodeExporter commented 9 years ago
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.

Original comment by d...@believecreative.com on 16 Nov 2011 at 5:03

GoogleCodeExporter commented 9 years ago
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.

Original comment by d...@believecreative.com on 16 Nov 2011 at 5:07

GoogleCodeExporter commented 9 years ago
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.

Original comment by sergei.l...@gmail.com on 17 Nov 2011 at 7:33

GoogleCodeExporter commented 9 years ago
Tried everything but no fix. So changing logger.

Original comment by d...@believecreative.com on 20 Nov 2011 at 10:39

GoogleCodeExporter commented 9 years ago
Do you want to say, that using other flash loggers solves your problem?

Original comment by sergei.l...@gmail.com on 22 Nov 2011 at 10:43

GoogleCodeExporter commented 9 years ago
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.

Original comment by d...@believecreative.com on 22 Nov 2011 at 10:47

GoogleCodeExporter commented 9 years ago
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.

Original comment by ch...@chrisfoster.com.au on 8 Dec 2011 at 3:31

GoogleCodeExporter commented 9 years ago
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.

Original comment by sergei.l...@gmail.com on 8 Dec 2011 at 8:21

GoogleCodeExporter commented 9 years ago
Trying to delete the log manually, windows says its open in "plugin container 
for firefox"

Original comment by AdamAd...@gmail.com on 30 May 2012 at 2:52

GoogleCodeExporter commented 9 years ago
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.

Original comment by sergei.l...@gmail.com on 30 May 2012 at 4:56

GoogleCodeExporter commented 9 years ago
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.

Original comment by ben.worl...@gmail.com on 21 Jun 2012 at 5:36

GoogleCodeExporter commented 9 years ago
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.

Original comment by sergei.l...@gmail.com on 21 Jun 2012 at 6:26

GoogleCodeExporter commented 9 years ago
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.  

Original comment by office1...@gmail.com on 17 Oct 2012 at 10:18