User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:33.0) Gecko/20100101 Firefox/33.0 (Beta/Release) Build ID: 20140710030200 Steps to reproduce: Open a link in a tab (either using the contextual menu or Command-click) Actual results: It doesn’t happen every time but most of the time the whole browser crashes Expected results: A new tab should have been opened

This was reported through about:crash but it looks like the system hasn’t actually linked this report to the crash. In case it’s needed this report is linked the crash at https://crash-stats.mozilla.com/report/index/11968e23-3d96-48da-909a-ef3332140712

A string of similar crashes today, the latest one being https://crash-stats.mozilla.com/report/index/bp-c197247c-6562-40f2-88dd-859742140714

This seems to be a duplicate of Bug 1026696

(In reply to Benjamin Kerensa [:bkerensa] from comment #3) > This seems to be a duplicate of Bug 1026696 Actually it does not has a totally different signature looking at the dump. I am not able to reproduce this on 20140713030204. Reporter what link is specifically crashing this? Is it specific sites? Also if you update to latest build are you still able to reproduce?

As far as I remember there’s no pattern, but it’s also intermittent so I don’t really have steps to reproduce it on demand. Most of the time it’s Facebook, but that’s only because I usually run Nightly when I’m running two browsers and I run Facebook on one browser and other stuff on the other browser. However, I’ve even seen it elsewhere including when I was testing a web site (self-hosted WordPress). (I kept relaunching Nightly until I gave up and ran Chrome because I did have to get the testing done…) I just updated to 20140713 and I’ll wait a few days before reporting if it crashes on the new Nightly. As I mentioned this is intermittent (though it was very frequent at least until 20140710); all I can do is to wait and see.

I also couldn't reproduce on nightly 33.0a1 (2014-07-19), OS X 10.9.2

It looks like this has been fixed. I haven’t seen a crash since 2014-07-13.

WFM based on comment 7

Can someone with the correct privs change the reason to FIXED? WORKSFORME is wrong. The bug was fixed, not unreproducible.

(In reply to Ambrose Li from comment #9) > Can someone with the correct privs change the reason to FIXED? WORKSFORME is > wrong. The bug was fixed, not unreproducible. Because we don't know what fixed this bug exactly (and also at this point, we don't want to burn time trying to find out what fixed it unless we have a really good reason), we don't mark it FIXED. FIXED would mean either a patch in this bug report fixed the bug, or (less commonly) some dependency fixed the bug. Because we don't have either of those things, we go for WORKSFORME instead to indicate that the bug is no longer rearing its head, but also to indicate, in this case, that the reason for its sudden disappearance is not fully known.