Closed Bug 1479340 Opened 7 years ago Closed 7 years ago

SEC_ERROR_UNKNOWN_ISSUER on various HTTPS site after a day without restarting Firefox

Categories

(Core :: Security: PSM, defect)

Product:
Core
Component:
Security: PSM
Version:
61 Branch
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED INCOMPLETE

People

(Reporter: dev, Unassigned, NeedInfo)

Details

Attachments

(9 files)

Certificate when the problem appears
73.22 KB, image/png
Details
pkcs11.txt profile #1
928 bytes, text/plain
Details
pkcs11.txt profile #2
900 bytes, text/plain
Details
pkcs11.txt profile #3
926 bytes, text/plain
Details
Firefox security devices windows
14.36 KB, image/png
Details
False positive wrong certificate bugzilla.mozilla.org
4.11 KB, text/plain
Details
Firefox Builtin Roots Module
13.25 KB, image/png
Details
Firefox Software Security Device stuck
18.21 KB, image/png
Details
Firefox Software Security Device displayed
17.16 KB, image/png
Details
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:61.0) Gecko/20100101 Firefox/61.0 Build ID: 20180704192850 Steps to reproduce: - start Firefox - browse https://support.mozilla.org or https://mail.google.com - wait for a day You'll find a lot of details including the cert chains and reports about many failed attempts to get around this at this place: https://support.mozilla.org/en-US/questions/1226671 Actual results: SEC_ERROR_UNKNOWN_ISSUER Expected results: the page loads correctly
I just noticed the automatic header of the bug description can be misleading: this is happening on Windows 10 and can be reproduced on many user accounts and many workstations. The bug does not occurs on Linux using the same Firefox version on the same network and environment. The bug occurs when people reload their page after a day. Dynamic web applications like GMail just stops to work with a custom GMail UI message and the Firefox's SEC_ERROR_UNKNOWN_ISSUER error is displayed if the user reload (F5) the tab. Users first noticed this bug months ago so it's a bug far older than Firefox 61 itself. The bug occurs on both 10586 and 17134 build of Windows 10 (so we can suppose it happens on all Windows 10 build).
It was asked me on #developers if certificates were the same, and I've check the ones for support.mozilla.org and I confirm they are the sames bytes to bytes. One interesting thing to know (as stated on support forum) is that users profiles (the %AppData% part) are stored on a nework share. The local part of the profile (the %LoalAppData% part for cache and other things like that) are stored on a physical drive. This is the only « uncommon thing » I see in that setup at first glance. The other thing is that a squid3 proxy is used but does nothing more on https connections than logging the domain names: no decyphering and other mitm tricks. The proxy is only used to cache http content and to log domains to adjust routing policies to improve user experience (like routing specific sites to faster lanes based on usage statistics). There is no custom enterprise CA.
I verified this issue on Windows 10 x64 with Firefox Nightly 63.0a1 (2018-08-01) (64-bit) and I cannot reproduce it after following your steps. Can you please test this in safe mode? Here is a link that can help you: https://goo.gl/AR5o9d. I think it will be a good idea to retest this on Firefox Nightly. Here is a link form where you can install Firefox Nightly: https://nightly.mozilla.org. If you still have the issue please create a new profile, you have the steps here: https://goo.gl/Awo6h8.
Flags: needinfo?(dev)
We do see the same bug. We use version 60.1.0esr (64-Bit) on windows 8.1. The problem only occurs after some time and is not easy to reproduce. The certificates are the same and it occurs for different sites, differen CAs and mutliple machines. I think it really might have to do with having %Appdata% on a network share like Thomas Debesse wrote. We also had a squid proxy but only on http and a disabled it and the problem still occured.
I'm unsuccessfully trying to reproduce it on my own computer but the error occurs on several computers from employees here. In the "Browser Console" I saw several errors like this: Error: Error(s) encountered during statement execution: disk I/O error Sqlite.jsm:807:25 Https connections are not possible anymore after that and a restart of firefox is the only solution. Any things i should check when it happens the next time on an empolyees computer?
We do have the same problems, while running Firefox on an Active Directory Windows 10 setup using GPO Folder Redirections to a network share as well. We did validate the problem using: * Firefox (61.0.2) in safe mode, it took <2h not using the pc for the problem to occur. Energy saving has been deactivated. * Firefox Nightly (downloaded 26.Aug.2018) in safe mode. Energy saving has been deactivated. The users profile had been recreated and the problem persists.
Component: Untriaged → Security: PSM
Product: Firefox → Core
It appears that there is an unfortunate workaround: I moved the profiles. I moved the users profiles away from the redirected %APPDATA%\Mozilla\Firefox\Profiles\ to C:\Users\<user>\FirefoxProfiles and edited the file *profiles.ini* afterwards to set the new absolute positions of the profiles. Using this the user who validated the problem 6 days ago had no problems during the last 4 days. I cross referenced the problem with the file servers latency and I found out that every time a user reported the problem the latency was between 1-2ms, our average latency to the file server is around 0.3ms. Not sure if this causes the problem but I thought it could be interesting.
Raffael, where can I find that console from you got this message? > Error: Error(s) encountered during statement execution: disk I/O error Sqlite.jsm:807:25 I would like to try to be able to reproduce it too. The idea of an issue related to the fact that the user profile is sitting on a network file-system does not look weird to me. In fact the people reporting it the most are ones of the few that are still at work late in the evening when others are not there anymore and when… backups start, increasing network usage significatively. Perhaps it can be related to a kind of timelimit issue due to network latency or thing like that. That's also why I would like to be able to reproduce that error message to see if 1. I can correlate this to some events, 2. I can reproduce it on demand (by increasing network load for example). Moving user profiles back from network share to local drive is neither a fix neither an acceptable workaround in this case. I hope this bug will get a fix because it makes Firefox unsuitable for this professional usage, and it's not good at all if Firefox becomes unsuitable for offices.
Flags: needinfo?(dev)
I think it was in the "Browser console". You can find it in the menu under "Web Developer" or by pressing Ctrl+shift+j
Does this still happen if you set the environment variable NSS_SDB_USE_CACHE to "yes"?
Flags: needinfo?(dev)
Status: UNCONFIRMED → RESOLVED
Closed: 7 years ago
Resolution: --- → INCOMPLETE
I driven some tests with a panel of users and they reported me seeing no difference and still experiencing the issue everyday.
Flags: needinfo?(dev)
Hi, users now report that the problem now occurs after only some hours (I noticed it myself), when before it was occurring after a workday. At the same time the number people reporting it is crazily increasing, especially since half-day working people are now experiencing it too! I've seen this bug marked as RESOLVED, what motivated this status change? How can I deploy a build that resolved that issue if exists?
Status: RESOLVED → REOPENED
Ever confirmed: true
Resolution: INCOMPLETE → ---
Hmm, I notice my Comment 11 was not explicit, when I said “I driven some tests with a panel of users” I meant those users used Firefox with NSS_SDB_USE_CACHE set to "yes" as requested by Dana Keeler. Hence the removing of needinfo flag.

Users report they still experience this bug with current Firefox.

Can you attach the file 'pkcs11.txt' from the profile directory of a user this happens to?

Flags: needinfo?(dev)

I'm using ff 60.5.0esr on RHEL 7 and have the same issue.

Here it happens today, very frequently, in less than an hour.
I have removed the xdg cache, looked at some straces when reloading the page with F5.
But found nothing obvious.

Martin, on a page you're seeing the error on, can you click "Advanced", click on the blue error code, click "Copy text to clipboard", paste that in a text file, and attach it to this bug? Thanks!

Flags: needinfo?(mvogt1)

Okay, if it occurs again.
Currently I'm thinking that the machine needed a reboot because afterwards it did not happen again.
Now it's working fine for two hours...

Flags: needinfo?(mvogt1)
Attached file pkcs11.txt profile #1 —
Flags: needinfo?(dev)
Attached file pkcs11.txt profile #2 —
Attached file pkcs11.txt profile #3 —

Ok - so it doesn't looks like pkcs11 modules are the problem. Same question as comment 18 I guess?

Flags: needinfo?(dev)

I just added 3 examples of pkcs11.txt from three profiles reported to reproduce the bug, first and second ones were running with NSS_SDB_USE_CACHE set to yes but unset with third one.

I anonymized the file server name and the user names btw.

Hmm, cross posting, will do as Comment 18 says.

Note that there was some copy-paste in https://support.mozilla.org/en-US/questions/1226671 , perhaps what you ask for.

Ok - that helps. How about if you look in about:preferences -> search for "security devices" -> click "Security Devices". What do you see in the "Security Modules and Devices" column? (I can figure out what the translation is if that would be helpful...)

Hi Dana, I see “NSS Internal PKCS #11 Module” and “NSS Builtin Objects”, see screenshot. Sorry for the late reply I did not receive the notification.

Flags: needinfo?(dev)

Just to be sure nothing is missing, this is an example of false-positive wrong certificate given when the problem occurs while browsing https://bugzilla.mozilla.org

Note that the message says wrongly that the connection is intercepted by a TLS proxy, which is wrong.

Also, this is some info about the given certificate, everything looks legit at this point:

$ openssl x509 -in bugzilla.mozilla.org-wrong-certificate.txt -text -noout
Certificate:
Data:
Version: 3 (0x2)
Serial Number:
09:b7:8a:c5:12:8b:f9:c4:2e:97:fd:e7:75:4f:01:73
Signature Algorithm: sha256WithRSAEncryption
Issuer: C = US, O = DigiCert Inc, CN = DigiCert SHA2 Secure Server CA
Validity
Not Before: Feb 8 00:00:00 2018 GMT
Not After : May 2 12:00:00 2019 GMT
Subject: C = US, ST = California, L = Mountain View, O = Mozilla Foundation, OU = WebOps, CN = *.bugzilla.mozilla.org
Subject Public Key Info:
Public Key Algorithm: rsaEncryption
RSA Public-Key: (2048 bit)
Modulus:
00:d5:af:ca:d2:d6:38:32:70:6c:1e:0e:d9:96:34:
29:8d:22:e0:e7:0e:78:79:ee:a2:b8:c9:c8:e4:9a:
73:82:ff:d5:0f:d1:d8:ce:22:19:03:eb:bd:9e:e3:
87:51:a2:b0:8c:b0:9e:e9:a0:41:2d:44:99:f6:73:
43:cd:60:85:91:49:ca:a7:4b:af:b7:17:1e:35:55:
0c:d4:22:c3:d5:f7:f6:89:ef:bf:1e:9a:09:6d:74:
17:c9:3d:41:82:2b:eb:50:ee:b5:87:64:f2:2f:dd:
56:4b:3b:91:0b:a0:39:84:f9:f9:95:73:08:82:99:
16:78:f4:b3:08:c2:c7:55:5a:8a:ef:5e:ed:b1:81:
00:9b:d0:b3:4c:53:63:fd:5e:7c:56:21:4d:2b:29:
15:45:98:0b:88:be:e4:74:83:71:f9:cc:a0:cc:0f:
b6:ad:ae:5b:04:d4:e8:42:f6:c2:97:60:8f:fb:f6:
11:fb:36:5c:fe:d7:59:5f:c6:83:94:ee:6c:2c:96:
50:f9:8b:2e:2a:51:53:f5:86:88:85:6c:74:12:9f:
6a:d8:e5:07:68:2d:a4:a5:c4:c5:92:9a:73:73:c0:
28:8f:cd:57:ab:73:da:2d:13:f4:2d:d0:5c:83:82:
ff:b2:6c:d3:39:09:c8:c4:14:a8:ac:e3:cb:b6:bf:
7e:07
Exponent: 65537 (0x10001)
X509v3 extensions:
X509v3 Authority Key Identifier:
keyid:0F:80:61:1C:82:31:61:D5:2F:28:E7:8D:46:38:B4:2C:E1:C6:D9:E2

        X509v3 Subject Key Identifier: 
            2A:8F:3F:30:BF:2F:77:E9:7C:7D:71:7F:FC:18:67:D3:4D:02:48:D0
        X509v3 Subject Alternative Name: 
            DNS:*.bugzilla.mozilla.org, DNS:bugzilla.mozilla.org
        X509v3 Key Usage: critical
            Digital Signature, Key Encipherment
        X509v3 Extended Key Usage: 
            TLS Web Server Authentication, TLS Web Client Authentication
        X509v3 CRL Distribution Points: 

            Full Name:
              URI:http://crl3.digicert.com/ssca-sha2-g6.crl

            Full Name:
              URI:http://crl4.digicert.com/ssca-sha2-g6.crl

        X509v3 Certificate Policies: 
            Policy: 2.16.840.1.114412.1.1
              CPS: https://www.digicert.com/CPS
            Policy: 2.23.140.1.2.2

        Authority Information Access: 
            OCSP - URI:http://ocsp.digicert.com
            CA Issuers - URI:http://cacerts.digicert.com/DigiCertSHA2SecureServerCA.crt

        X509v3 Basic Constraints: critical
            CA:FALSE
        CT Precertificate SCTs: 
            Signed Certificate Timestamp:
                Version   : v1 (0x0)
                Log ID    : BB:D9:DF:BC:1F:8A:71:B5:93:94:23:97:AA:92:7B:47:
                            38:57:95:0A:AB:52:E8:1A:90:96:64:36:8E:1E:D1:85
                Timestamp : Feb  8 20:48:00.733 2018 GMT
                Extensions: none
                Signature : ecdsa-with-SHA256
                            30:44:02:20:7D:E2:44:9E:D8:F9:7F:AE:11:69:3D:4D:
                            29:60:74:A2:DA:4E:D3:7A:89:31:84:C8:2A:07:EB:0A:
                            48:82:1B:EC:02:20:1F:2D:FD:E4:40:14:70:86:FF:33:
                            B0:C1:46:C0:5A:E2:A4:13:2E:42:58:68:E7:8B:7A:DC:
                            4A:BC:21:B4:18:A9
            Signed Certificate Timestamp:
                Version   : v1 (0x0)
                Log ID    : 87:75:BF:E7:59:7C:F8:8C:43:99:5F:BD:F3:6E:FF:56:
                            8D:47:56:36:FF:4A:B5:60:C1:B4:EA:FF:5E:A0:83:0F
                Timestamp : Feb  8 20:48:00.736 2018 GMT
                Extensions: none
                Signature : ecdsa-with-SHA256
                            30:46:02:21:00:94:91:73:82:6B:40:D5:CD:0D:78:00:
                            82:47:C1:F8:F5:56:B8:37:F4:B3:DC:FA:E8:29:C3:D2:
                            F3:61:7C:CD:52:02:21:00:BA:35:2E:C0:E4:B7:4E:38:
                            B6:56:DE:2E:47:D2:69:E2:67:E9:16:54:02:FC:19:82:
                            1F:AA:BC:68:3E:13:22:8B
Signature Algorithm: sha256WithRSAEncryption
     6d:1e:af:fd:54:1b:85:47:89:e5:df:08:82:52:07:5a:62:0f:
     74:94:5b:da:ec:db:5f:31:95:36:58:b5:6e:ab:a5:4e:88:9f:
     ef:3e:d6:ce:13:4a:3e:52:52:cf:2b:5e:40:8a:b8:13:53:36:
     52:c4:f1:95:c8:fb:ca:12:2f:ad:4e:7c:ad:a9:af:40:bf:5a:
     12:19:e6:be:4a:78:a6:bb:1d:c0:83:77:4b:0d:fc:b1:1e:da:
     69:67:30:7b:e6:2d:51:0e:1b:bf:4c:b4:a4:1c:3f:b2:f3:3c:
     f4:aa:5e:97:4d:a0:b0:f8:04:28:bd:c4:37:94:3f:16:a5:e9:
     cf:87:bb:c3:61:0a:82:fb:c1:a7:02:f1:ec:1d:81:23:dd:fc:
     e1:f1:96:2d:f7:70:cd:4e:ec:71:56:9c:48:93:81:34:b7:0b:
     60:0a:ef:fb:45:95:2d:80:09:dd:e1:31:2d:f3:a4:87:9a:da:
     e4:bc:14:b1:c2:c6:16:91:2f:89:b8:e6:2e:f0:58:cd:b1:a1:
     a6:5f:3b:1b:23:ec:e4:a1:b9:ed:c4:95:58:26:7c:af:bd:aa:
     db:12:1b:d0:22:c1:0a:df:23:87:7b:5d:fa:ed:a8:2b:2d:f7:
     3d:78:db:d8:71:84:97:11:a1:73:dc:97:cb:ec:25:86:8b:5f:
     2b:8f:49:49

[illwieckz@gollum:/tmp] $ openssl x509 -in 20190218.false-positive-wrong-certificate.bugzilla.mozilla.org.txt -text -noout
Certificate:
Data:
Version: 3 (0x2)
Serial Number:
09:b7:8a:c5:12:8b:f9:c4:2e:97:fd:e7:75:4f:01:73
Signature Algorithm: sha256WithRSAEncryption
Issuer: C = US, O = DigiCert Inc, CN = DigiCert SHA2 Secure Server CA
Validity
Not Before: Feb 8 00:00:00 2018 GMT
Not After : May 2 12:00:00 2019 GMT
Subject: C = US, ST = California, L = Mountain View, O = Mozilla Foundation, OU = WebOps, CN = *.bugzilla.mozilla.org
Subject Public Key Info:
Public Key Algorithm: rsaEncryption
RSA Public-Key: (2048 bit)
Modulus:
00:d5:af:ca:d2:d6:38:32:70:6c:1e:0e:d9:96:34:
29:8d:22:e0:e7:0e:78:79:ee:a2:b8:c9:c8:e4:9a:
73:82:ff:d5:0f:d1:d8:ce:22:19:03:eb:bd:9e:e3:
87:51:a2:b0:8c:b0:9e:e9:a0:41:2d:44:99:f6:73:
43:cd:60:85:91:49:ca:a7:4b:af:b7:17:1e:35:55:
0c:d4:22:c3:d5:f7:f6:89:ef:bf:1e:9a:09:6d:74:
17:c9:3d:41:82:2b:eb:50:ee:b5:87:64:f2:2f:dd:
56:4b:3b:91:0b:a0:39:84:f9:f9:95:73:08:82:99:
16:78:f4:b3:08:c2:c7:55:5a:8a:ef:5e:ed:b1:81:
00:9b:d0:b3:4c:53:63:fd:5e:7c:56:21:4d:2b:29:
15:45:98:0b:88:be:e4:74:83:71:f9:cc:a0:cc:0f:
b6:ad:ae:5b:04:d4:e8:42:f6:c2:97:60:8f:fb:f6:
11:fb:36:5c:fe:d7:59:5f:c6:83:94:ee:6c:2c:96:
50:f9:8b:2e:2a:51:53:f5:86:88:85:6c:74:12:9f:
6a:d8:e5:07:68:2d:a4:a5:c4:c5:92:9a:73:73:c0:
28:8f:cd:57:ab:73:da:2d:13:f4:2d:d0:5c:83:82:
ff:b2:6c:d3:39:09:c8:c4:14:a8:ac:e3:cb:b6:bf:
7e:07
Exponent: 65537 (0x10001)
X509v3 extensions:
X509v3 Authority Key Identifier:
keyid:0F:80:61:1C:82:31:61:D5:2F:28:E7:8D:46:38:B4:2C:E1:C6:D9:E2

        X509v3 Subject Key Identifier: 
            2A:8F:3F:30:BF:2F:77:E9:7C:7D:71:7F:FC:18:67:D3:4D:02:48:D0
        X509v3 Subject Alternative Name: 
            DNS:*.bugzilla.mozilla.org, DNS:bugzilla.mozilla.org
        X509v3 Key Usage: critical
            Digital Signature, Key Encipherment
        X509v3 Extended Key Usage: 
            TLS Web Server Authentication, TLS Web Client Authentication
        X509v3 CRL Distribution Points: 

            Full Name:
              URI:http://crl3.digicert.com/ssca-sha2-g6.crl

            Full Name:
              URI:http://crl4.digicert.com/ssca-sha2-g6.crl

        X509v3 Certificate Policies: 
            Policy: 2.16.840.1.114412.1.1
              CPS: https://www.digicert.com/CPS
            Policy: 2.23.140.1.2.2

        Authority Information Access: 
            OCSP - URI:http://ocsp.digicert.com
            CA Issuers - URI:http://cacerts.digicert.com/DigiCertSHA2SecureServerCA.crt

        X509v3 Basic Constraints: critical
            CA:FALSE
        CT Precertificate SCTs: 
            Signed Certificate Timestamp:
                Version   : v1 (0x0)
                Log ID    : BB:D9:DF:BC:1F:8A:71:B5:93:94:23:97:AA:92:7B:47:
                            38:57:95:0A:AB:52:E8:1A:90:96:64:36:8E:1E:D1:85
                Timestamp : Feb  8 20:48:00.733 2018 GMT
                Extensions: none
                Signature : ecdsa-with-SHA256
                            30:44:02:20:7D:E2:44:9E:D8:F9:7F:AE:11:69:3D:4D:
                            29:60:74:A2:DA:4E:D3:7A:89:31:84:C8:2A:07:EB:0A:
                            48:82:1B:EC:02:20:1F:2D:FD:E4:40:14:70:86:FF:33:
                            B0:C1:46:C0:5A:E2:A4:13:2E:42:58:68:E7:8B:7A:DC:
                            4A:BC:21:B4:18:A9
            Signed Certificate Timestamp:
                Version   : v1 (0x0)
                Log ID    : 87:75:BF:E7:59:7C:F8:8C:43:99:5F:BD:F3:6E:FF:56:
                            8D:47:56:36:FF:4A:B5:60:C1:B4:EA:FF:5E:A0:83:0F
                Timestamp : Feb  8 20:48:00.736 2018 GMT
                Extensions: none
                Signature : ecdsa-with-SHA256
                            30:46:02:21:00:94:91:73:82:6B:40:D5:CD:0D:78:00:
                            82:47:C1:F8:F5:56:B8:37:F4:B3:DC:FA:E8:29:C3:D2:
                            F3:61:7C:CD:52:02:21:00:BA:35:2E:C0:E4:B7:4E:38:
                            B6:56:DE:2E:47:D2:69:E2:67:E9:16:54:02:FC:19:82:
                            1F:AA:BC:68:3E:13:22:8B
Signature Algorithm: sha256WithRSAEncryption
     6d:1e:af:fd:54:1b:85:47:89:e5:df:08:82:52:07:5a:62:0f:
     74:94:5b:da:ec:db:5f:31:95:36:58:b5:6e:ab:a5:4e:88:9f:
     ef:3e:d6:ce:13:4a:3e:52:52:cf:2b:5e:40:8a:b8:13:53:36:
     52:c4:f1:95:c8:fb:ca:12:2f:ad:4e:7c:ad:a9:af:40:bf:5a:
     12:19:e6:be:4a:78:a6:bb:1d:c0:83:77:4b:0d:fc:b1:1e:da:
     69:67:30:7b:e6:2d:51:0e:1b:bf:4c:b4:a4:1c:3f:b2:f3:3c:
     f4:aa:5e:97:4d:a0:b0:f8:04:28:bd:c4:37:94:3f:16:a5:e9:
     cf:87:bb:c3:61:0a:82:fb:c1:a7:02:f1:ec:1d:81:23:dd:fc:
     e1:f1:96:2d:f7:70:cd:4e:ec:71:56:9c:48:93:81:34:b7:0b:
     60:0a:ef:fb:45:95:2d:80:09:dd:e1:31:2d:f3:a4:87:9a:da:
     e4:bc:14:b1:c2:c6:16:91:2f:89:b8:e6:2e:f0:58:cd:b1:a1:
     a6:5f:3b:1b:23:ec:e4:a1:b9:ed:c4:95:58:26:7c:af:bd:aa:
     db:12:1b:d0:22:c1:0a:df:23:87:7b:5d:fa:ed:a8:2b:2d:f7:
     3d:78:db:d8:71:84:97:11:a1:73:dc:97:cb:ec:25:86:8b:5f:
     2b:8f:49:49

(In reply to Thomas Debesse from comment #27)

Created attachment 9044573 [details]
Firefox security devices windows

Hi Dana, I see “NSS Internal PKCS #11 Module” and “NSS Builtin Objects”, see screenshot. Sorry for the late reply I did not receive the notification.

Thanks! If you open that dialog again and select the second module ("Module de base intégré") is its path ("Chemin", I gather) on a network share? Is it in the same directory as the Firefox installation? Is the file specified available when connections start failing?

Flags: needinfo?(dev)

If you open that dialog again and select the second module ("Module de base intégré")

  • Is its path ("Chemin", I gather) on a network share? → No
  • Is it in the same directory as the Firefox installation? → Yes
  • Is the file specified available when connections start failing? → Yes

Well, for the later I guess Yes since once I've noticed the failing I can read the file, by the way it's on a hard drive so I doubt the file become unavailable, this is the file path:

C:\Program Files\Mozilla Firefox\nssckbi.dll
Flags: needinfo?(dev)

I noticed that since Firefox caught the bug, when I click on “Software Security Device” it can't display the content without being stuck first. The window become white-gray, Windows says the window is not responding, then a pop-up appears saying that chrome://global/content/elements/stringbundle.js:42 is busy and does not respond. Once I click on “Continue” the content is displayed.

It seems to occur any time I click on “Software Security Device” after having clicked elsewhere. The Device Manager window was already opened when the security bug happened. It was not occurring before the security bug happened (I only tested at startup by the way).

This is how the “Software Security Device” is displayed after being stuck and having clicked on “Continue”.

Odd - can you capture a profile using https://perf-html.io/ while that is happening?

Flags: needinfo?(dev)
Status: REOPENED → RESOLVED
Closed: 7 years ago → 7 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: