246 bytes, text/html
117.76 KB, image/jpeg
133.44 KB, image/jpeg
Created attachment 330323 [details] Watches window is blocked (see the difference with the Local variables window) No action become possible : nor remove or add watches, nor expand or contract level on watches tree.
Related bug : 410943 (see below) The last version without this bug is 0.9.87 (but is not compatible with firefox 3) In version 0.9.87.1 and 0.9.87.2 it was not possible to see more than 1 level (see bug 410943) The version 0.9.87.3 partially fixes the previous issue but has the same behaviour as mentionned here in version 0.9.87.4
Summary: Watches crash when expand two levels (or +) on an array of array whose value is changed → Watches crash when expanding two levels (or +) and values change
Version: unspecified → Trunk
Message error in interactive session : !! Internal error processing hook "watches:hook-debug-stop". !! [Exception... "Component returned failure code: 0x80040111 (NS_ERROR_NOT_AVAILABLE) [jsdIStackFrame.eval]" nsresult: "0x80040111 (NS_ERROR_NOT_AVAILABLE)" location: "JS frame :: chrome://venkman/content/venkman-records.js :: vr_evalstring :: line 644" data: no]
http://developer.mozilla.org/en/docs/How_to_get_a_stacktrace_with_WinDbg http://developer.mozilla.org/en/docs/Using_the_Mozilla_source_server please set a breakpoint on jsdStackFrame::Eval and then trace through to find out what's actually going wrong.
i'm not actively working on this area. atm i'm busy worrying about microb and mxr.
Internal error processing hook “watches:hook-debug-stop”. [Exception... "Component returned failure code: 0x80040111 (NS_ERROR_NOT_AVAILABLE) [jsdIStackFrame.eval]" nsresult: "0x80040111 (NS_ERROR_NOT_AVAILABLE)" location: "JS frame :: chrome://venkman/content/venkman-records.js :: vr_evalstring :: line 644" data: no] This isn't actually a crash... and so not critical. It just throws errors, and seems to be similar to bug 458020.
Severity: critical → normal
So the errors mean, apparently, that ASSERT_VALID_EPHEMERAL; fails: http://mxr.mozilla.org/seamonkey/source/js/jsd/jsd_xpc.cpp#1909 Mrbkap, jorendorff, could you please tell me what that means? Because I don't understand it (not the word EPHEMERAL, nevermind what it's supposed to be checking and/or what Vnk is doing wrong, nor most importantly how to fix it). :-)
Status: UNCONFIRMED → NEW
Ever confirmed: true
Summary: Watches crash when expanding two levels (or +) and values change → Watches window stops updating and throws errors in certain cases
Sorry for all the bugspam, this new Bugzilla UI is driving me nuts. Anyway, jorendorff, mrbkap, could you please look at comment #9? Thanks!
Created attachment 342722 [details] Wrong values in watches in opposite of Local Yes, this bug seems to be related to Bug 458020. In order to be more explicit, I've joined a new screen shot. We see that the value of arr1 is 3 in Local Variables (it's right) and 2 in Watches (WRONG) and that a sign minus (-) is present before arr1 in Local and Watches but there is nothing to collapse /expand in Watches (opposite of Local witch details arr1 arr1, ...) In Watches, if we click on the node sign -/+, the sign +/- switches but nothing changes. To reproduce : 1)Load the file as before mentioned. 2)set a break point on line => arr1=[3,2]; (the value of arr1 changes) 3) add arr1 as watch 4) expand two levels to see a tree like below : - arr1 + 0 + 1 - 2 #0 #1 5) press F12 to go to the next line 6) the windows crashes and is out of service(see Interactive image): wrong value of arr1, impossible to expand or minimize the different nodes, ...
It regressed since the resolution of Bug 410943. The latest version without this bug is Version 0.9.87 (not compatible with Firefox 3) Version Version 0.9.87.1 didn't display any multiple watches (Bug 410943). Version 0.9.87.2 displayed again multiple watches (Bug 410943 fixed!?) but with this new bug, not fixed since. I'm sure of that because, due to this bug, after testing the different new versions, I kept Version 0.9.87 until the migration to Firefox 3 for compatibility reason.
Component is obsolete so resolving bugs as INCOMPLETE
Status: NEW → RESOLVED
Last Resolved: 3 days ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.