What steps will reproduce the problem? 1. Construct a very large object (how much large: see below), then call $firePHP->log($theObject,'large object') 2.When HTML page displayed in Firefox, go the Console tab and hover or click the 'large object' line to display its contents

What is the expected output? What do you see instead? Should display the object contents, but never achieves it.

What version of the product are you using? On what operating system? FirePHP core 0.2.1 with Firefox 1.4.0a22 under WinXP.

Please provide any additional information below. At the moment, I can't propose an exact method to reproduce the problem. Especially I don't know which is the "sufficient" object size to cause it to happen, since I precisely needed to deep examine my object through FirePHP, in order to see if it was constructed as I expected.

Here attached are two files: - the HTTP headers (FirePHP_hang_with_large_object.txt) - a screenshot of task handler window (FirePHP_hang_with_large_object.jpg) showing that, after regularly increasing (as we could expect), past a certain time the memory usage is alternatively increasing and decreasing, as if a part of the job already done was cyclicly lost and rebuilt

I omitted an interesting information: print_r() does not fail to display this object contents. So we know it is not malformed in any way nor out of acceptable size limits.