>>What steps will reproduce the problem?<<

1. Write code to log some output to Firebug+FirePHP like in this article: http://www.christophdorn.com/Blog/2008/09/02/firephp-and-zend-framework-16/

2. Make sure your page uses doubleclick ads in it. (I'm sorry I can't tell you how to set that part up, because I'm working w/ client code that already has doubleclick ads on it. I have nothing to do w/ that side of things..)

3. Play some music in a background window w/ http://www.pandora.com .

>>What is the expected output? <<

I expect to see debug output logged to the Firebug console.

>>What do you see instead?<<

The output is logged, but intermittently, and apparently at random, the console just clears the screen and all that output is gone. But if I click on the net panel and expand it and look at the HEADERs, I do see that the right calls were sent to the console.

>>What version of the product are you using? On what operating system?<<

ZF 1.62 and latest versions of firebug+firephp. My OS is XP.

>>Please provide any additional information below.<<

Normally one tab shouldn't affect another tab, but in this case, because doubleclick is all over the net, your page calls the same domain as that running in another tab. I guess there's a document.write or some kind of page refresh in the other tab on the same domain that causes the refresh on this tab.

In fact, I've seen cases where I'll run the Zend_Log code to Firebug console in two separate tabs and the active tab will receive logging info from the other tab. So obviously if you're in the same domain space, they are talking to each other.

One last note, Pandora refreshes their ad calls between pretty much every song. Hence lots of refreshes to cause unexpected screen clears if you don't think to associate what happens in a second tab to what's happening in your tab...

Is this still an issue with 0.4.2: http://www.firephp.org/HQ/FinalRelease.htm ?

The situation is much better. Pandora doesn't cause much trouble. But still some intermittent problems here and there...I wish I could identify a specific cause though...but I suppose you can close this issue.

1.0 will fix the remaining issues.