When the JIT is disabled, interpreterThrowInCaller does not handle the exception throw correctly.
Created attachment 209987 [details] patch
Comment on attachment 209987 [details] patch a layout test result changed. Running additional check to confirm will upload new patch soon
Created attachment 209991 [details] patch 2 added error was caught in layout test.
Is this a mistake in the layout test that setCaptionDisplayMode is not present?
Comment on attachment 209991 [details] patch 2 Clearing flags on attachment: 209991 Committed r154817: <http://trac.webkit.org/changeset/154817>
All reviewed patches have been landed. Closing bug.
(In reply to comment #4) > Is this a mistake in the layout test that setCaptionDisplayMode is not present? I thought so as well, but running the test through chrome and Firfox recieves the same error.
(In reply to comment #7) > (In reply to comment #4) > > Is this a mistake in the layout test that setCaptionDisplayMode is not present? > > I thought so as well, but running the test through chrome and Firfox recieves the same error. It was a bug in the test which was fixed earlier this morning in http://trac.webkit.org/changeset/154815.
(In reply to comment #8) > (In reply to comment #7) > > (In reply to comment #4) > > > Is this a mistake in the layout test that setCaptionDisplayMode is not present? > > > > I thought so as well, but running the test through chrome and Firfox recieves the same error. > > It was a bug in the test which was fixed earlier this morning in http://trac.webkit.org/changeset/154815. yes, it looks like both patches were going in at the same time. Im not sure how to adjust for this if anything. If further action is required on my part let me know. Thanks
(In reply to comment #9) > (In reply to comment #8) > > (In reply to comment #7) > > > (In reply to comment #4) > > > > Is this a mistake in the layout test that setCaptionDisplayMode is not present? > > > > > > I thought so as well, but running the test through chrome and Firfox recieves the same error. > > > > It was a bug in the test which was fixed earlier this morning in http://trac.webkit.org/changeset/154815. > > yes, it looks like both patches were going in at the same time. Im not sure how to adjust for this if anything. Next time you might ping someone that knows the area (me, jer.noble), or file a bug instead of just blindly checking in obviously failing results. > If further action is required on my part let me know. Thanks Dino fixed the results earlier this morning.