Certain page crashes FF 29a1

RESOLVED DUPLICATE of bug 953057

Status

()

Core
Security: PSM
--
critical
RESOLVED DUPLICATE of bug 953057
4 years ago
4 years ago

People

(Reporter: User Dderss, Unassigned)

Tracking

(Depends on: 1 bug)

29 Branch
x86_64
Windows 7
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(crash signature, URL)

(Reporter)

Description

4 years ago
User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:29.0) Gecko/20100101 Firefox/29.0 (Beta/Release)
Build ID: 20131224030203

Steps to reproduce:

I tried to open the following page: http://forum.ixbt.com/topic.cgi?id=45:14048


Actual results:

FireFox 29a1 has crashed; I have tried it twice:
https://crash-stats.mozilla.com/report/index/6c054420-d497-4155-a357-e62e32131224
https://crash-stats.mozilla.com/report/index/bp-9d14b989-f946-4b08-9e31-c04822131224


Expected results:

A page for a discussion thread should have been opened.
(Reporter)

Updated

4 years ago
Crash Signature: nsCMSSecureMessage::decode(char const*, unsigned char**, int*)
Hardware: x86 → x86_64

Updated

4 years ago
Severity: normal → critical
Crash Signature: nsCMSSecureMessage::decode(char const*, unsigned char**, int*) → [@ nsCMSSecureMessage::decode(char const*, unsigned char**, int*)]
Component: Untriaged → Security: PSM
Product: Firefox → Core
No crash here on win32 Nightly builds from today's date, cset:
https://hg.mozilla.org/mozilla-central/rev/c0f85061c7d3
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:29.0) Gecko/20100101 Firefox/29.0

64bit issue ?
WFM with my own build from Dec 22. User Dderss, can you confirm that this started with your build? If not, can you try to find the build it started on?

Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:29.0) Gecko/20100101 Firefox/29.0
(Reporter)

Comment 3

4 years ago
Since I filed this bug ever update that FF 29a1 has this crash.

I am not sure at all that this crash started from the time when I encountered the bug. Where can I find older builds of FF 29a1-64 to try to find from when this crash has appeared?
You can get older Win64 nightlies from here:
http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/

You want the ones that are labeled firefox-29.0a1.en-US.win64-x86_64.

BTW, have you been able to reproduce in safe mode?
Still can't reproduce on a current build. Please check to see if you can reproduce in safe mode.
(Reporter)

Comment 6

4 years ago
Wonderful coincidence, but this bug is now gone with the newest update I just applied.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → INVALID
(Reporter)

Comment 7

4 years ago
Alas, I was glad prematurely.

I do not know why did not catch the crash yesterday, but today it is still on. To be sure that it is purely 64-bit issue, I tested the link with in fully updated FF 29a1 32-bit, which did not cause crash, and in fully updated FF 29.0a1 64-bit in Safe mode, which resulted in crash:
http://crash-stats.mozilla.com/report/index/4c86d9f6-91c4-4ece-a9ef-480872131229

I also installed earliest 64-bit build that is accessible, FF 28.0a1 (from November), which resulted in crash, too:
http://crash-stats.mozilla.com/report/index/4b037356-c681-42a4-8750-b66ad2131229

This means that this is old issue.
Status: RESOLVED → UNCONFIRMED
Resolution: INVALID → ---
(Reporter)

Comment 8

4 years ago
It looks like this but depends on passwords list bug #953057, because this is signature I caught this time:

nsSecretDecoderRing::decode(char const*, unsigned char**, int*) 

And additional signature:

xul.dll@0x11d2fe2 | xul.dll@0x11d3e94 | xul.dll@0x1a09110 | xul.dll@0x11d6222 | xul.dll@0x130a12 | xul.dll@0x1a09110 | xul.dll@0x8feefd | xul.dll@0x8df2cd | mozjs.dll@0x2cee28
Depends on: 953057
No crash on Nightly x64 29.0a1 (2014-01-08), Win 7 x64.
Do you still reproduce this ?
(Reporter)

Comment 10

4 years ago
Please see reply on the dependent bug (the bug is actually the same):
http://bugzilla.mozilla.org/show_bug.cgi?id=953057#c15
Status: UNCONFIRMED → RESOLVED
Last Resolved: 4 years ago4 years ago
Resolution: --- → DUPLICATE
Duplicate of bug: 953057
You need to log in before you can comment on or make changes to this bug.