1243742 - Crash with shutdownhang in nsThread::Shutdown() when visiting http://www.pferdekaemper.de/ with Safe Browsing enabled

Status: RESOLVED DUPLICATE of bug 1164518

(Core :: XPCOM, defect)

Description

[bob]

User Agent: Mozilla/5.0 (X11; Fedora; Linux x86_64; rv:43.0) Gecko/20100101 Firefox/43.0
Build ID: 20151229124331

Steps to reproduce:

Started Firefox with standard config and called Domain pferdekaemper.de; Browser loads for 3 minutes then crashes; under Windows 7/10 and Ubuntu; checking with LiveHTTPHeaders one can see many Posts to safebrowsing.google.com; with Security features for SafeBrowsing deactivated the site loads normally;


Actual results:

Browser loads for 3 minutes then crashes; under Windows 7/10 and Ubuntu; checking with LiveHTTPHeaders one can see many Posts to safebrowsing.google.com


Expected results:

site should have loaded in 1-2 secs like with all other tested browsers like chrome, opera, safari, IE, Edge

Comment 1

[Loic]

Did you test with a fresh profile?
https://support.mozilla.org/en-US/kb/profile-manager-create-and-remove-firefox-profiles

Comment 2

[Loic]

Ok, I reproduced it:
https://crash-stats.mozilla.com/report/index/d4dcf070-92ba-4d57-94a1-800d62160128

Surely dupe of bug 1204809

Comment 3

[bob]

The problem is still there also in the 44 Branch.
When you call the site it loads 1-2 minutes and sends many POSTS to safebrowsing.google.com.
Could you reproduce this as well? once you deactivate the security options, it no longer sends the POSTS and the site loads normally.
Thanks

Comment 4

[Loic]

(In reply to Loic from comment #2)
> Ok, I reproduced it:
> https://crash-stats.mozilla.com/report/index/d4dcf070-92ba-4d57-94a1-
> 800d62160128
> 
> Surely dupe of bug 1204809

In fact not, patch from bug 1204809 doesn't fix this issue. So these 2 bugs have the same generic crash signature but different underlying causes.

Comment 5

[Loic]

Latest Nightly CR:
https://crash-stats.mozilla.com/report/index/1d2e1a90-b6cf-43f6-8a6f-10e922160208

Comment 6

[Loic]

kats, could you find someone at Mozilla who can look at this bug, please.

Comment 7

[Kartikaya Gupta (email:[e-mail])]

Yoric, the crash in comment 5 is hitting the watchdog it looks like, do you know who should look into this?

Comment 8

[Loic]

For the record: in this bug https://bugzilla.mozilla.org/show_bug.cgi?id=1204809#c30 jimm suggests to track all the bugs with this signature.

Comment 9

[David Teller [:Yoric] - still alive but not very active]

(In reply to Kartikaya Gupta (email:[e-mail]) from comment #7)
> Yoric, the crash in comment 5 is hitting the watchdog it looks like, do you
> know who should look into this?

Sorry, no idea. The watchdog is just there to convert hangs into crashes, but I have no clue what's causing the hang.

Comment 10

[Kartikaya Gupta (email:[e-mail])]

Ok, thanks. gcp, since this seems to happen only when safebrowsing is enabled (see comment 0), can you take a look? I'm guessing the safebrowsing is causing a hang which the watchdog is turning into a crash. I tried to repro briefly on a local Linux build but couldn't - although I notice the website has a message up warning users not to use Firefox because of this issue, so it's probably a widespread issue.

Comment 12

[Gian-Carlo Pascutto [:gcp]]

FWIW the underlying issue is that one of the base URLs of pferdekaemper.de collides with some known malware or phishing site, so all the resources on the page cause an alert that we then have to verify. 

The database is generally constructed to make this as uncommon as possible (Chrome and Safari will also load the site a bit slower than normal because they use the same DB), but Firefox is beyond gruesomely slow in this case, and that's something we have to fix.

The issue with this specific site will eventually fix itself as soon as the malware/phishing entry that collides expires.