User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:220.127.116.11) Gecko/20101026 Firefox/3.6.12 Build Identifier: 0.9.88.1 After a few simple trace actions (e.g. Step Into), Venkman freezes with no apparent CPU/HDD/etc. usage and browser has to be restarted. Tracing is impossible. Reproducible: Always Steps to Reproduce: Firefox ver.: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:18.104.22.168) Gecko/20101026 Firefox/3.6.12 1. Go to http://www.google.com/firefox?client=firefox-a&rls=org.mozilla:en-US:official, open Venkman, open source (I usually open it via Open Windows->Browser Window->[html filename] 2. Set a breakpoint on first JS line and reload the page 3. When control is transferred to Venkman, press Step Into a few times to trace the code Actual Results: After one or a dozen presses, the image in the left side of Venkman (Open Windows/Local Variables/Breakpoints) becomes corrupted and Venkman is frozen. Sometimes Venkman's own code shows up in the Source Code window, maybe it gets stuck trying to trace itself...
I am noticing that Venkman freezes up but I'm not seeing this behavior: > Sometimes Venkman's own code shows up in the Source Code window, maybe it gets > stuck trying to trace itself... so maybe there are two different things going on here. Do you have "Exclude Application Files" checked in the Debug menu?
Most definitely yes
In that case, I don't think you should be seeing any of Venkman's code, since it's part of the "Application files". Maybe post a snippet of what code you're seeing that seems to be part of Venkman?
Here's an example of what I usually see: http://i.imgur.com/S0Mf2.jpg (window image corruption) And here's what happens when I press Stop button (to stop at next line of JS) http://i.imgur.com/skzAo.png (venkman sources)
RE: Konstantin Svist; these are exactly the two problems I am currently having with venkman in Linux. I'm using Debian Sid's mozilla-venkman 0.9.88.1-1 package with iceweasel 3.5.19-2.
(In reply to comment #5) > RE: Konstantin Svist; these are exactly the two problems I am currently > having with venkman in Linux. I'm using Debian Sid's mozilla-venkman > 0.9.88.1-1 package with iceweasel 3.5.19-2. Forgot to mention: I can reliably recreate the window corruption/lock up issue every time I encounter a document.write call while stepping manually through a script.
One more thing: Its pretty clear that it starts by initially trying to debug its own components. This makes the STOP button effectively useless, but you can still set breakpoints to find the lockup/screen corruption bug instead.
There've been enough reports of this (and I've seen it myself) that I have to mark this one as NEW.
Status: UNCONFIRMED → NEW
Ever confirmed: true
You need to log in before you can comment on or make changes to this bug.