crash in nss3.dll@0x1d69e0




4 years ago
4 years ago


(Reporter: mats, Unassigned)



Windows NT

Firefox Tracking Flags

(firefox36- affected)


(crash signature)



4 years ago
This bug was filed from the Socorro interface and is 
report bp-b6c39948-d389-4920-a0ea-3def52141105.

[Tracking Requested - why for this release]:
This is a new startup crash in Nightly that appears to have started
around 2014-11-05.

More crash incidents at:

Comment 1

4 years ago
Oh, it seems to be 64-bit only.  I suspect this signature is also related (it started
at the same time) and it has a better stack:  bp-a15c68f2-215c-4118-8d69-7ce222141105

More at:|+wajam_goblin_64.dll%400x387d0&range_value=28#tab-reports
Crash Signature: [@ nss3.dll@0x1d69e0] → [@ nss3.dll@0x1d69e0] [@ nss3.dll@0x1d69e0 | wajam_goblin_64.dll@0x387d0 ]
Hardware: All → x86_64

Comment 2

4 years ago
And another signature that looks like the same problem:
Crash Signature: [@ nss3.dll@0x1d69e0] [@ nss3.dll@0x1d69e0 | wajam_goblin_64.dll@0x387d0 ] → [@ nss3.dll@0x1d69e0] [@ nss3.dll@0x1d69e0 | wajam_goblin_64.dll@0x387d0 ] [@ nss3.dll@0x1da9e0 ]
Startup crash, tracking.
status-firefox36: --- → affected
tracking-firefox36: ? → +

Comment 4

4 years ago
Kai or Wan-Teh, do you have an idea what the problem might be here?


4 years ago
Crash Signature: [@ nss3.dll@0x1d69e0] [@ nss3.dll@0x1d69e0 | wajam_goblin_64.dll@0x387d0 ] [@ nss3.dll@0x1da9e0 ] → [@ nss3.dll@0x1d69e0] [@ nss3.dll@0x1d69e0 | wajam_goblin_64.dll@0x387d0 ] [@ nss3.dll@0x1da9e0 ] [@ nss3.dll@0x1d69e0 | GetFileInfo ]

Comment 5

4 years ago
I believe there weren't any NSS upgrades on mozilla-central around 2014-11-05 (I was on vacation and didn't see any activity).

In all threads, I see wajam_goblin_64.dll that calls NSS.

Could that be the issue?

Searching the web, I see that Chromium has apparently blacklisted that library, and other reports, who claim the library is trying to inject something into the application and is a potential threat.
David, do you think we should blacklist this lib too? Thanks
Flags: needinfo?(dmajor)
I'm not a big fan of these Wajam libraries, but lmandel has a contact over there. Let's give them a chance first.
Flags: needinfo?(dmajor) → needinfo?(lmandel)
I sent a request to Wajam to review this bug today. I'll report back if and when I hear from them.
Flags: needinfo?(lmandel)

Comment 9

4 years ago
"We’re not sure what WajamPage.exe is, but after a quick Google, it becomes clear that it’s yet another browser hijacker and we’re lucky it didn’t install."
Wajam confirms that this bug is fixed in the latest version.

(In reply to Mats Palmgren (:mats) from comment #9)
> "We’re not sure what WajamPage.exe is, but after a quick Google, it becomes
> clear that it’s yet another browser hijacker and we’re lucky it didn’t
> install."

To be clear, my working with Wajam is not an endorsement of their product. We should take appropriate actions to protect Firefox users as always. However, some number of users will have Wajam installed on their systems. For these users, I think it is preferable that Firefox not crash and so I am happy to pass on crash and related information to Wajam to help them improve the stability of both of our products.
Lawrence, any news from them? Thanks
Flags: needinfo?(lmandel)
No but I'm not sure that I should expect any. I think the original timeline they gave for rolling out the fix puts it somewhere at the beginning of Feb. We should try to confirm that the crash signature has disappeared in order to close this bug.
Flags: needinfo?(lmandel)
There is not much we can do here. Not tracking anymore.
tracking-firefox36: + → -
As far as I can tell there isn't any cause for concern in current crash-stats. wajam_goblin signatures pretty much disappeared by early December.
Last Resolved: 4 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.