Closed Bug 586499 Opened 9 years ago Closed 9 years ago

TM: Yarr mochitest failure browser_plainTextLinks.js

Categories

(Core :: JavaScript Engine, defect)

x86_64
Linux
defect
Not set

Tracking

()

RESOLVED FIXED

People

(Reporter: cdleary, Assigned: cdleary)

References

Details

(Whiteboard: fixed-in-tracemonkey)

Attachments

(1 file)

TEST-START | chrome://mochikit/content/browser/browser/base/content/test/browser_plainTextLinks.js
TEST-INFO | chrome://mochikit/content/browser/browser/base/content/test/browser_plainTextLinks.js | Console message: [JavaScript Error: "regular expression too complex" {file: "chrome://browser/content/browser.js" line: 8021}]
NEXT ERROR TEST-UNEXPECTED-FAIL | chrome://mochikit/content/browser/browser/base/content/test/browser_plainTextLinks.js | Timed out
TEST-UNEXPECTED-FAIL | chrome://mochikit/content/browser/browser/base/content/test/browser_plainTextLinks.js | Found a tab after previous test timed out: data:text/html,Test%20For%20Non-Hyperlinked%20url%20selection
TEST-INFO | checking window state
TEST-END | chrome://mochikit/content/browser/browser/base/content/test/browser_plainTextLinks.js | Test took 30041ms to complete
STR: TEST_PATH=browser/base/content/test/browser_plainTextLinks.js
EXTRA_TEST_ARGS='--debugger=gdb' make -C objdir-ff-debug/
mochitest-browser-chrome
Looks like I missed the addition of the opcode-sized OP_BRAZERO in counted-repeats... each of the 16 bracket repetitions are prefixed by an OP_BRAZERO here. The assertion was firing because the pre-computed regexp bytecode program length was too small.
Attachment #465062 - Flags: review?(gal)
I forgot to `hg add` the test for this... will be sure to do that before I check in. It was just the offending regexp /^(?:\s*){0,16}/ compilation crash test.
Attachment #465062 - Flags: review?(gal) → review+
http://hg.mozilla.org/tracemonkey/rev/5bbae07fd403
Whiteboard: fixed-in-tracemonkey
Flags: in-testsuite+
http://hg.mozilla.org/mozilla-central/rev/5bbae07fd403
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.