1852780 - the splunk web page displaying search results stalls and become unresponsive

Status: RESOLVED WORKSFORME

(Core :: Performance: General, defect)

Description

[patpro]

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

Steps to reproduce:

To reproduce this problem you need an access to a splunk enterprise with enough data indexed.

I have reproduced this problem on macOS 13.5.1 and 13.5.2 (macbook M1 pro and macmini M2 pro) with FF 117 and FF nightly 119.0a1, both fresh browser installs.

open the splunk URL and go to the search app
start a "big enough" search
if problem does not occur right away, open another tab with a different splunk search, etc.

it might be a problem with the macOS 13.5 release. Latest FF and macOS updates where very close in the timeline. Chrome & Safari are OK, thought.

Actual results:

results are starting to render for few seconds then the wep page appears to be stuck: buttons & links are not working any longer but when you click a button or menu item ("Dashboard" for example) the location bar is updated to the new URL but the rendered page never updates.

Expected results:

results are rendered properly and the web page is usable.

Comment 1

[BugBot [:suhaib / :marco/ :calixte]]

The Bugbug bot thinks this bug should belong to the 'Firefox::Search' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Comment 2

[patpro]

I’ve made a short recording of this problem: https://perso.univ-lyon2.fr/~pproniew/ffbug-splunk092023.mp4

Comment 3

[Ardelean Oana, Desktop Test Engineering [:oardelean]]

Hello, thank you for the bug report !
I tried to reproduce your issue but I was unsuccessful. Unfortunately I do not have access to a splunk enterprise, and searching within the page did not cause any freezes/stalls. Would you be so kind as to answer a few questions so we can investigate this further?

• Does this issue happen when Firefox is in Troubleshoot Mode? Here’s a link on how to enable it: https://support.mozilla.org/en-US/kb/diagnose-firefox-issues-using-troubleshoot-mode#w_how-to-start-firefox-in-troubleshoot-mode
• Does this issue happen on any other websites/pages?

Moving the Component to ‘General’. Please change if there’s a better fit, thank you.

Comment 4

[patpro]

Hi,

You can freely install and run Splunk Enterprise but I reckon it’s a bit complex. If we can’t find a cause and/or work-around I might setup a dummy splunk instance loaded with innocuous data for you to test.

After a full day testing I can’t reproduce the bug when FF is in trouble shoot mode. And as soon as I quit trouble shoot mode the problem comes back.
This does not explain why the problem occurs on a fresh FF install on a fresh macOS VM or on a fresh FF Nightly install on my laptop.

As far as I can tell the problem does not occur on any other web site. It only occurs on the app/search/search web page of a Splunk Enterprise server. Any other Splunk Enterprise page is OK.

Comment 5

[Marco Bonardo [:mak]]

Hello, could you please take a performance profile when the problem happens?
The page https://profiler.firefox.com has instructions, then you can share the profile here in the report and we can investigate where the time is being spent. The Network profile type should be good to start with.

Comment 6

[patpro]

You’ll find a profiler trace here: https://share.firefox.dev/457nHe8
Thanks a lot!

Comment 7

[BugBot [:suhaib / :marco/ :calixte]]

This bug was moved into the Performance component.

:github, could you make sure the following information is on this bug?

• ✅ For slowness or high CPU usage, capture a profile with http://profiler.firefox.com/, upload it and share the link here.
• For memory usage issues, capture a memory dump from about:memory and attach it to this bug.
• Troubleshooting information: Go to about:support, click "Copy raw data to clipboard", paste it into a file, save it, and attach the file here.

If the requested information is already in the bug, please confirm it is recent.

Thank you.

Comment 8

[patpro]

Attachment: memory-report.json.gz

Comment 9

[patpro]

Attachment: about-support.txt

Comment 10

[Andrew Creskey [:acreskey]]

The impact calculator rated this as low, although this looks like to be a serious problem.

The Performance Impact Calculator has determined this bug's performance impact to be low. If you'd like to request re-triage, you can reset the Performance Impact flag to "?" or needinfo the triage sheriff.

Platforms: macOS
Impact on browser: Renders browser effectively unusable
Websites affected: Rare

Comment 11

[Andrew Creskey [:acreskey]]

Thanks for filing this, patpro.
We didn't see the browser being locked up in the provide performance profile, Comment 6.
Can I ask you to try again?

Comment 12

[patpro]

Hello
I'm very sorry for the delay.
I will try to get a new performance profile ASAP, but I'm not sure it will be different.
The browser is showing the problematic behaviour in the profile I sent. It's important to understand that the browser is not locked up: its current web page display is no longer refreshed, but if I switch to another window or another tab, it's working great. Also, clicking on the links inside the frozen web page will successfully update the location bar.

Despite recent updates of FF, I'm still experiencing this problem +10 times a day. I will provide a new performance profile as soon as possible, but hiding confidential information is pretty tricky.

Comment 13

[Andrew Creskey [:acreskey]]

Thanks Patpro.
When you capture a new profile, can you:
• Select the "Graphics" option from Firefox Profiler Settings dropdown
• Then click on "Edit settings" and enable "Screenshots"

Comment 14

[patpro]

Hello everyone, I'm sorry for the very (very!) late update. I couldn't find any time to make more profiling but I have a good news. The current Firefox release does not show the bug. Since the last update, I am unable to reproduce the problem. I hope the problem is fixed and won't come back. Many thanks to every Firefox contributors.

Comment 15

[Andrew Creskey [:acreskey]]

Thanks for re-testing this, patpro.
If you see the problem re-appear, please re-open the bug.