Hi Philipp, I just made an http log with the 1st of the 3 builds provided by Noah. This log is made in Firefox safe mode.

1st part : https://pastebin.mozilla.org/8914349 2nd part : https://pastebin.mozilla.org/8914350 3rd part : https://pastebin.mozilla.org/8914351

(had to separate in 3 parts because pastebin crashed when I pasted more than 500 lines)

For personal reasons, I replaced the URL of the Firefox home page with COMPANY_INTRANET_URL

thanks, could you do one with firefox 49.0.1 as well?

Philipp,

Really sorry : 49.0.1 process starts, but does not fill the log file (the file is created, but remains empty, even if I wait more than 60 seconds).

Starting Firefox in safe mode does not change anything.

Just to be sure it was not a profile issue, I renamed my profile folder before starting 49.0.1 with the http log options, but I get the same result.

you have probably read it in the bug as well, apparently the syntax for running http log has changed in 49.

could you try producing the http log with 49.0.1 again but instead use:

set MOZ_LOG=timestamp,rotate:200,nsHttp:5,nsSocketTransport:5,nsStreamPump:5,nsHostResolver:5,io:5 

many thanks!

Even with this syntax, FF 49.0.1 does not fill the log file

See my screenshot here

Really sorry...

This matches my experience. When it hung, 49.0.1 hung very quickly before you could find out anything about what was going on and didn't appear to get as far as actually doing anything excepting starting the processes that hung. I reverted to 48.0.2 and can't take this computer down to run debug tests, so many thanks to assistance-multi for doing all this work.

When Mozilla has found and fixed the bug, I will try upgrading to the version after that, confirm that add-ons work ok with the new interface and that the hanging issue has gone away.

assistance-multi said

Even with this syntax, FF 49.0.1 does not fill the log file See my screenshot here Really sorry...

please don't be sorry - we should say sorry for all the hassle & troubleshooting steps... we are very thankful for you hanging in there!

one more slight change that a network developer has recommended to try & see if a proper log is generated then would be this:

set MOZ_LOG=sync,timestamp,rotate:200,nsHttp:5,nsSocketTransport:5,nsStreamPump:5,nsHostResolver:5,io:5

As a developer, I feel sorry for you, knowing how hard it can be to solve a bug !

Anyway, the new syntax seems ok : 3 lines are written in the log file, so I paste it directly here :

2016-09-30 11:50:51.193000 UTC - [Main Thread]: D/nsSocketTransport STS dispatch [4c202e0] 2016-09-30 11:50:51.193000 UTC - [Socket Thread]: D/nsSocketTransport STS thread init 1000 sockets 2016-09-30 11:50:51.193000 UTC - [Socket Thread]: D/nsSocketTransport PollableEvent() using socket pair

(that's all folks !)

Note : I've launched it 3 times to be sure, getting exactly the same result each time.

Just a detail : not sure if it can help, but holding the shift key while trying to launch FF 49.0.1 does not change anything : the FF window explaining that FF will be started in safe mode does not show.

Uninstalling Kaspersky Anti-Virus solves the problem.

https://bugzilla.mozilla.org/show_bug.cgi?id=1305436#c24

Silly question but I want to make sure: Are you able to browse the web normally without any issues?

I don't have Kaspersky installed, I use MS Security Essentials for anti-virus and ZoneAlarm Free. I have checked the MS SE log and it contains no relevant event, neither do the System management system and application logs. The ZoneAlarm log is not available after this time.

Firefox 49.0.1 doing something that causes the anti-virus to stop it or having been changed in a manner incopmatible with Windows APIs for security products would be consistent with it stopping rapidly, abruptly and with no output. As I had the issue with an add-in not running and unable to get to its library (perhaps C++, it didn't say), the way the new add-on interface runs software and interacts with the Windows security APIs looks well worth exploring by the Firefox developers.

In answer to Naoh, yes, everything works absolutely fine with Firefox 48.0.2, reliability, web browsing, add-ins, no issues. It's just 49.0.1.

And Chrome, which uses that same interface as apparently introduced in Firefox 49 is working fine too, so there isn't a problem with the interface per so it's only Firefox with issues, so would be its use of the interface.

Noah_SUMO said

Are you able to browse the web normally without any issues?

Yes Noah_SUMO, it works normally.

Thanks for your antivirus info & confirming you don't have Kaspersky installed, Kevin.

Glad to hear that assistance-multi!

From reading the bug now, the devs have a plan of action and will work on it accordingly.

so far it was suspected that it was a code-change regarding the networking component in firefox that caused this issue but your and another user's testing doesn't seem to corroborate this...

in case you still have a way to reproduce this isse could you please try to run these (final) 3 builds and report back with the results of each, if you are at least able to get the interface to open?:

• build 1
• build 2
• build 3

...then we'd have checked every single change within the regression range and could pin down the issue exactly.

Hi Philipp, I reinstalled Kaspersky Anti-Virus and tried the 3 builds. For the 3, I have the same result : the interface starts, but Firefox still can't connect to any url.

thanks a lot & just to be sure that reinstalling kaspersky didn't generally change the conditions, could you also re-test https://archive.mozilla.org/pub/firefox/try-builds/archaeopteryx@coole-files.de-3d23b6dfd423f4dfef4dac906719720267d9fc6a/try-win32/firefox-52.0a1.en-US.win32.installer.exe which you mentioned wasn't working before to confirm that it's still not working...

This build has the original problem : firefox starts, runs in background, but does not open UI.