Closed Bug 476192 Opened 16 years ago Closed 16 years ago

TM: Assertion failure: JSVAL_TAG(v) == JSVAL_STRING during Topsitetest on http://www.sauto.cz/

Categories

(Core :: JavaScript Engine, defect, P2)

1.9.1 Branch
x86
macOS
defect

Tracking

()

VERIFIED FIXED

People

(Reporter: cbook, Assigned: gal)

References

()

Details

(Keywords: assertion, testcase, verified1.9.1)

Attachments

(2 files, 3 obsolete files)

Attached file gdb stack
Found during the automated TopSite Test on http://www.sauto.cz/ http://www.sauto.cz/ cause a Assertion failure: Assertion failure: JSVAL_TAG(v) == JSVAL_STRING, at /work/mozilla/builds/1.9.1-tracemonkey/mozilla/js/src/jstracer.cpp:1582
Flags: blocking1.9.1?
Attached file testcase (obsolete) —
Attached file shell testcase (obsolete) —
Moved to the shell (just had to remove the <script> tags) and removed a few empty blocks and functions. Now 28 lines.
Attachment #359794 - Attachment is obsolete: true
Attached file shell testcase, 25 lines (obsolete) —
A little simpler: made some variables local, killed shadowing (!!) in loadAds.
Attachment #359855 - Attachment is obsolete: true
Can't reduce it much more than this.
Btw, this assertion also shows up in bug 475658.
Confirmed.
Attachment #359858 - Attachment is obsolete: true
Flags: blocking1.9.1? → blocking1.9.1+
Priority: -- → P2
Assignee: general → gal
Flags: blocking1.9.1+ → blocking1.9.1?
Priority: P2 → --
Flags: blocking1.9.1? → blocking1.9.1+
Priority: -- → P2
Note this is not fixed by Bug 475916 - i still see this with a TM tip build
Flags: in-testsuite?
Flags: in-litmus-
(In reply to comment #4) > Created an attachment (id=359861) [details] > shell testcase, 9 lines > > Can't reduce it much more than this. This testcase seems to WFM in TM js shell (with and without -j), would like more confirmation before resolution.
(In reply to comment #7) > Note this is not fixed by Bug 475916 - i still see this with a TM tip build This WFM as well. Tomcat, can you still reproduce it?
Gary, can you use the auto bisecter to determine which changeset fixed this?
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
(In reply to comment #10) > Gary, can you use the auto bisecter to determine which changeset fixed this? autoBisect shows bug 476653 is likely to have fixed this. changeset: 25401:0d0489b3e4b7 user: David Anderson date: Tue Feb 24 22:52:09 2009 -0500 summary: Fixed breakage of type stability guarantees between linked trees, and fixed using the wrong global typemap in LeaveTree (bug 476653, r=gal). I've not yet manually verified this though.
http://hg.mozilla.org/tracemonkey/rev/488f2529b447 /cvsroot/mozilla/js/tests/js1_5/Regress/regress-476192.js,v <-- regress-476192.js initial revision: 1.1
Flags: in-testsuite? → in-testsuite+
(In reply to comment #11) > (In reply to comment #10) > > Gary, can you use the auto bisecter to determine which changeset fixed this? > > autoBisect shows bug 476653 is likely to have fixed this. > > changeset: 25401:0d0489b3e4b7 > user: David Anderson > date: Tue Feb 24 22:52:09 2009 -0500 > summary: Fixed breakage of type stability guarantees between linked trees, > and fixed using the wrong global typemap in LeaveTree (bug 476653, r=gal). > > I've not yet manually verified this though. I have manually verified that the fix in bug 476653 does indeed fix this issue as well.
Status: RESOLVED → VERIFIED
Depends on: 476653
No longer depends on: sisyphus-tracking
Bug 476653 is fixed1.9.1, so this is too.
Keywords: fixed1.9.1
v 1.9.1, 1.9.2
fix summary to not include string 'Assertion fail' /cvsroot/mozilla/js/tests/js1_5/Regress/regress-476192.js,v <-- regress-476192.js new revision: 1.2; previous revision: 1.1
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: