This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Avatar for Username

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

This thread was archived. Please ask a new question if you need help.

Issues since FF 64 Beta13

  • 5 replies
  • 1 has this problem
  • 8 views
  • Last reply by TyDraniu

boris.hoeffgen
boris.hoeffgen
more options

Hey, since FF 64 B13 there are some changes which broke our APP but I cannot find a solution. When we log into our internal website, we are immediately logged out again as soon as I click a link there. You can see that after loading the page, a control cookie "CmdCookie" is reset to an initial value so that you are directed to the login page. All other cookies remain unchanged. With FF64 Beta 12 everything worked without any problems. Does anyone know where the problem could be? If I turn off all the chaches then I can log in, but sporadically I keep being kicked out.

Thanks in advance and have a nice day! Max

Hey, since FF 64 B13 there are some changes which broke our APP but I cannot find a solution. When we log into our internal website, we are immediately logged out again as soon as I click a link there. You can see that after loading the page, a control cookie "CmdCookie" is reset to an initial value so that you are directed to the login page. All other cookies remain unchanged. With FF64 Beta 12 everything worked without any problems. Does anyone know where the problem could be? If I turn off all the chaches then I can log in, but sporadically I keep being kicked out. Thanks in advance and have a nice day! Max

All Replies (5)

TyDraniu
TyDraniu
  • Top 10 Contributor
more options

There's not much changes between these versions, I can't say what would be the cause of this issue.

https://hg.mozilla.org/releases/mozilla-beta/pushloghtml?fromchange=FIREFOX_64_0b12_RELEASE&tochange=FIREFOX_64_0b13_RELEASE

boris.hoeffgen
boris.hoeffgen Question owner
more options

I was wrong, it must be one of the following changes https://hg.mozilla.org/releases/mozilla-beta/pushloghtml?fromchange=FIREFOX_64_0b11_RELEASE&tochange=FIREFOX_64_0b12_RELEASE

Do you have any ideas how I can localize the error?

TyDraniu
TyDraniu
  • Top 10 Contributor
more options

Bug 1503696 looks suspicious.

If you could run MozRegression, it would point to a problematic commit. With that knowledge you could file a new bug on bugzilla.

boris.hoeffgen
boris.hoeffgen Question owner
more options

I just used mozregression with the following command: mozregression --build-type shippable --find-fix --good 2018-11-15 --bad 2018-11-17

I can see, that nighly build 2018-11-15 is OK and 2018-11-16 contains the issue but I get the info: 

2:23.47 INFO: Got as far as we can go bisecting nightlies...
2:23.47 INFO: Last good revision: 0051c8d339a969d80b66e6ce243091a9dbb6a319 (2018-11-15)
2:23.47 INFO: First bad revision: 7154eb3601f3b89ef5b8e559c9f2bae57f6d59f3 (2018-11-16)
2:23.47 INFO: Pushlog:

https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=0051c8d339a969d80b66e6ce243091a9dbb6a319&tochange=7154eb3601f3b89ef5b8e559c9f2bae57f6d59f3 

2:23.47 INFO: Switching bisection method to taskcluster
2:23.48 INFO: Getting mozilla-central builds between 0051c8d339a969d80b66e6ce243091a9dbb6a319 and 7154eb3601f3b89ef5b8e559c9f2bae57f6d59f3
2:39.60 INFO: There are no build artifacts for these changesets (they are probably too old).

When I compare https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=0051c8d339a969d80b66e6ce243091a9dbb6a319&tochange=7154eb3601f3b89ef5b8e559c9f2bae57f6d59f3 with https://hg.mozilla.org/releases/mozilla-beta/pushloghtml?fromchange=FIREFOX_64_0b11_RELEASE&tochange=FIREFOX_64_0b12_RELEASE

I can see that Bug 1503696 is included in both lists. Am I correct to download the sources from Firefox 64 beta 12 and remove the changes from the bug and recompile it? Then should I be able to test it?

TyDraniu
TyDraniu
  • Top 10 Contributor
more options

You could be able to test it, but there's no need to download sources etc. The only change in this bug (except tests) is inside the FaviconLoader.jsm, which is compressed within the omni.ja file. Try to open this omni.ja with 7-zip, edit the FaviconLoader.jsm and save it back, it should be enough to test it.