User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:98.0) Gecko/20100101 Firefox/98.0

Steps to reproduce:

On our local server-based Jira (help.geneseo.edu), open the page for any help ticket.

Actual results:

Page mostly loads, but hangs with the throbber never finishing. This appears to have some connection to the part of the page for entering a new comment to add to the ticket.
Problem goes away in Troubleshoot Mode. Problem also goes away if I disable fission.autostart and restart Firefox. This is true whether I have all add-ons, etc, disabled or enabled.

Expected results:

Loading should complete with at most minor delay.

Hi James! Would it be possible to record a log following these instructions ? Please note that it might contain private data, so you might want to share it via mail.

Thanks for your support!

Set release status flags based on info from the regressing bug 1732358

I'd be happy to share some logs, but I'm not sure how to set the environment variables under macOS so that they are effective for running GUI apps. I tried "export"ing in .zshenv and restarting, and that certainly set them in an xterm. But no log file was created whether I start firefox from the GUI or from the command line with "open -a". At least, a Finder file search couldn't find that file name. Maybe I just don't know where to look for the log file? Or maybe I should be specifying a full file path?

Oops. Resetting the Needinfo flag. I didn't mean to clear it with the previous comment.

Process while creating these log files:

• environment set to MOZ_LOG=ProcessIsolation:5,DocumentChannel:5,SessionHistory:5 and MOZ_LOG_FILE=[full path to desktop]
• open firefox from command line to a URL listing my tickets in Jira
• click link to open a browser page with one of the tickets
• allow page load to hang for 30 seconds (page mostly loads OK, throbber on throughout that time)
• use menu Firefox> Quit
• windows close immediately, but application continues to hang for 72 seconds before fully quitting

NOTE: Opening Firefox directly to the ticket URL does not cause the hang. Accessing from the page with list of tickets consistently causes the hang, unless fission has been disabled.

Thanks a lot! I am not the right person to look at these logs, but the other ni?'d people are most likely very interested.

James, do you think it would be possible to get an account on that jira instance?
(Mozilla does use Jira through Atlassian internally and I haven't heard of issues with that instance.)

oh, I guess I can just create an account. Now I just need to figure out what to load there to reproduce the issue.

I don't know if you could get an account on this Jira, but I could ask my IT team. Note that we are not on cloud Jira/Atlassian, although we will be transitioning to cloud in the next 12 months. I have no idea if that relates to this problem.

In case it helps, I had the same problem using Safari 15.3, but it seems to have gone away in Safari 15.4.
When I first raised this, I am not sure that my IT folks could reproduce. But I get it consistently even in a fresh local account, and the problem always goes away by setting about:config> fission.autostart to false, then restart Firefox.

So I did manage to create an account but I don't know how to get to " open the page for any help ticket.".

Recreating needinfo to send a new email about it.

@Olli, what did you do to "create an account"? Where is that account? If I can also create an account on whatever instance you are using, I could then check whether I see the same behavior that I see on our local instance.

I don't know whether our local instance has been customized, but once signed in to Jira, in the upper right next to the personal avatar there is a button "Requests." That button takes me to a list of tickets that I have created on the system. Following one of those links takes me to the page for that specific ticket, which is where I experience the fission conflict.

smaug@welho.com in https://jira.geneseo.edu

Do you have exact steps to reproduce the issue there?

The steps to reproduce /were/ as simple as in the original posting ("open the page for any help ticket"). This was true with 100% regularity, over the course of many months, at least six.
However, I have just re-tested, and the issue has gone away. Impossible to know what has removed the conflict, but this trouble report can be resolved. I'm not sure how to do that; hopefully someone else can do it for me?

Thanks for testing. If this is indeed gone, let's resolve as worksforme.