I reported same bug for linux, and Ben for Mac, so OS -> All.
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Windows 7 → All
Hardware: x86 → All
It seems to have appeared between the 10/12 nightly and the 10/13 nightly, which should be this window: http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=2593c8c8af8b&tochange=f6e81dd5a125
I'm not the Dave you're looking for. Luckily one of them (dmandelin) is CC'ed. CC'in another (dvander). Dave #24601
I haven't heard of any plans to turn on chrome for the method JIT, but if there's a correctness issue, it's worth diagnosing since it could affect content too.
Thanks for the info. In that case, it sounds like this is not something we will look at or focus on for the Firefox 4 timeline.
Priority: -- → P2
Target Milestone: --- → Future
No longer blocks: 597043
Yeah, at least keep testing -- best case, the crashes go away. Less likely but could be a lifesaver if content hits the same bug, we get some crucial diagnostic information. Please leave any such skidmarks here if you get them. /be
I use JM for chrome. I saw no improvement with Panorama compared to TM only. :(
9 years ago
Assignee: general → dvander
Status: NEW → ASSIGNED
This affects the web but it's pretty obscure - you need to have a constructor that, inside a catch block, returns an object other than |this|. In chrome it's easier because it can also trigger with "let". The bug is that constructors weren't checking fp->rval before assuming an implicit return (RETRVAL, STOP) are returning undefined.
Attachment #494529 - Flags: review?(dmandelin)
Attachment #494529 - Flags: review?(dmandelin) → review+
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.