605282 - Firefox 4.0 Beta 6 pt-BR fails: ProfileSwitchSocketsStillActive

Status: RESOLVED WORKSFORME

(Core Graveyard :: Security: UI, defect)

Description

[Gustavo Cainelli]

User-Agent:       Mozilla/5.0 (Windows NT 5.0; rv:2.0b6) Gecko/20100101 Firefox/4.0b6
Build Identifier: Mozilla/5.0 (Windows NT 5.0; rv:2.0b6) Gecko/20100101 Firefox/4.0b6

When I start Firefox 4.0 Beta 6 Portuguese Brazil version on Windows 2000 Service Pack 5, appears the following warning message: "The operation was not completed due to an internal failure. A secure communication was not established correctly." (A operação não foi concluída devido a uma falha interna. Uma comunicação segura não foi estabelecida corretamente.) The browser opens with two empty tabs, and must close it and reopen to work properly. If you need more information about the error please request me.



Reproducible: Always

Steps to Reproduce:
1.Star Firefox 4.0 B6 Portuguese Brazil on Windows 2000
2.See empty tabs
3.Close and reopen Firefox
Actual Results:  
After reopen firefox, it works correctly without giving any error message.

Expected Results:  
Do not see any error message when opening

I also have Firefox 3.6.10 installed on this operating system and this message doesn't appears in this version.

Comment 1

[Gustavo Cainelli]

Attachment: pt-BR pipnss: ProfileSwitchSocketsStillActive

Comment 2

[timeless]

Comment on attachment 484101 [details]
pt-BR pipnss: ProfileSwitchSocketsStillActive

http://mxr.mozilla.org/l10n-central/source/pt-BR/security/manager/chrome/pipnss/pipnss.properties#387

387 ProfileSwitchSocketsStillActive=A operação não foi concluída devido a uma falha interna. Uma comunicação segura não foi estabelecida corretamente.

Comment 3

[timeless]

this comes from nsNSSShutDownList::areSSLSocketsActive() returning true...

in theory this should do something useful if run from a cmd.exe prompt:

set NSPR_LOG_MODULES=pipnss:5
set NSPR_LOG_FILE=%homepath%\pipnss.log
"c:\program files\mozilla firefox\firefox.exe"

might work, but it depends on whether or not FORCE_PR_LOGGING was included in the build -- which it probably wasn't. Someone would need to get a custom build to make this work :(

Comment 4

[Gustavo Cainelli]

I tried the procedure but didn't works. Let's wait for the next version of Firefox 4. This message began to appear from beta 5 version, probably for some aggregate function int that version.

Thanks anyway!

Comment 5

[timeless]

waiting isn't really going to help....

use the 32bit version of windbg,
https://developer.mozilla.org/En/How_to_get_a_stacktrace_with_windbg

[ensure firefox isn't running...]

before you do 'g', do:
bu nsNSSShutDownList::trackSSLSocketCreate "kp; g"
bu nsNSSShutDownList::trackSSLSocketClose "kp; g"
bu nsNSSShutDownList::areSSLSocketsActive "kp; g"

click "add an attachment" and attach the resulting log file.

Comment 6

[:Cykesiopka]

Bug 807757 removed the string and the code that calls nsNSSShutDownList::areSSLSocketsActive():
https://hg.mozilla.org/mozilla-central/rev/6b34780b29a6