Closed Bug 1687576 Opened 5 years ago Closed 3 years ago

Print and print preview take 35 seconds to respond in Firefox 84.0.2

Categories

(Core :: Printing: Output, defect)

Product:
Core
Component:
Printing: Output
Version:
Firefox 84
Type:
defect

Tracking

()

Status:
RESOLVED DUPLICATE of bug 1686983

People

(Reporter: madoscher, Unassigned)

References

Details

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

Steps to reproduce:

  1. Opened tab in yahoo.com
  2. Clicked on Print under File
  3. Waited 35 seconds for correct print prompt response
  4. Same lengthy response occurred after clicking on Print Preview in PDF option

Actual results:

After 35 seconds the correct print prompt appeared

Expected results:

Should not take 35 seconds.
In Chrome and Safari, the response to "print" using yahoo.com is 1 second or less as does "print preview."

My wife has macbook Air where problem occurs. It uses macOS Sierra v 10.12.6.
My macbook Pro is new and uses macOS Catalina 10.15.7 The print delay does not occur on my macbook.
I have gone through the recommended changes to jprefs file removing all items beginning with ""print."" And changing the item beginning with ""print_""
Curiously the ""print"" option worked several times after changing the jprefs file --- until I tried the "print preview" using PDF option in lower LH corner of print prompt screen. Then problem recurred.
I have compared the items in the config listing using my config list and my wife's. I noted no differences.

Comment from Jonathan Watt in Firefox user support:

Hi MikeDos. This site is intended for helping end users with using Firefox, but what you're describing sounds like a bug. Would you mind reporting this over on the Mozilla issue tracker at https://bugzilla.mozilla.org/ where the developers would be better able to help you? If you do that, can you also mention over there which versions of macOS the macbook pro and macbook air are running?

Bugbug thinks this bug should belong to this component, but please revert this change in case of error.

Component: Untriaged → Printing: Output
Product: Firefox → Core

Thanks for the report. Would you mind capturing a performance profile (steps below) while the print operation is happening, on the affected laptop? That would help us figure out what Firefox is doing during the wasted time.

To do that, you'd do the following:

  1. visit https://profiler.firefox.com/ and click "Enable profiler menu button"; that should make a "speedometer" icon show up on your Firefox toolbar.
  2. Click the dropdown arrow next to that new Firefox toolbar icon, and in its Settings dropdown, choose "Firefox Platform".
  3. Click "Start recording" (or click the toolbar icon itself).
  4. Reproduce the bug.
  5. Click the toolbar icon again to end/capture the performance profile. This will open a new tab with a visualization.
  6. Click "Upload" at the top right of the new tab's profile visualization.
  7. Share the resulting URL (after the upload has completed)

Note that by default, the profile includes screenshots and URLs of tabs that you have open, so privacy-wise, you may want to perform these steps in a Firefox session that doesn't have any other tabs open. Alternately/also, you can opt to redact different things using checkboxes in the Upload dialog.

Flags: needinfo?(madoscher)

Subject: Re: [Bug 1687576] Print and print preview take 35 seconds to respond in Firefox 84.0.2
hmmm.
Always wanted to know how to perform a trace in current technology.
I ran the share URL but don't know whether it gets to you identified well enough to know which problem it is addressing.
Note that this time the print prompt came up real fast but getting to "print preview" took the full 30 seconds.

I'd certainly be glad to run the sequence again if the results did not get really shared properly.

Thanks, Mike
PS: Occasionally a similar delay comes up for my wife on her Macbook Air for opening Yahoo.com. I tell her to leave it open in a separate tab but for some reason she resists.

Flags: needinfo?(madoscher)

Hi Mike -- thanks for following up! Sorry, I wasn't clear -- when I said "Share the resulting URL", I meant "copy & paste the resulting URL to this bug report". :) It should give you a URL like https://share.firefox.dev/[some unique ID].

Would you mind trying again and providing that URL here?

Did a print preview after print screen immediately popped up. Took over 30 seconds for the preview. Then did a "print". Took maybe 20 to 30 seconds.
Here's the URL:
https://share.firefox.dev/39luhti

Mike
Sorry to take so long.

ooops looks like share URL is:
https://share.firefox.dev/39luh1i
Had to manually copy from the problem laptop to mine.

Thanks, Mike!

Those URLs are broken, but it looks like it's probably a capital-i-vs-lowercase-L problem. If I replace the "l" in you URL with a "I", I get the following link which works [EDIT: I mistyped it too the first time, but I've fixed it now]:
https://share.firefox.dev/39Iuh1i
I think that's your profile. :)

Would you mind sharing the URL that you were printing/print-previewing here? (It's redacted in the profile you provided, so I can't tell what it is.) That would help with reasoning about what's going on, if we can try printing/print-previewing the same URL on our end. Alternately, if you could pick some public URL that doesn't require login (e.g. https://www.example.org/ or https://wiki.mozilla.org/Main_Page or something else ) and could try print-previewing or printing that & provide a profile along with the URL, that would be great too.

Anyway, going with what we've got right now: from looking at your profile, it does indeed look like there's about a ~1 minute delay for a Print Preview operation, followed by a ~1 minute delay for a Print operation. (PBrowser::Msg_Print and PBrowser::Msg_PrintPreview) It's not clear to me what's going on there, though; both of them are spending nearly all of their time in poll, which means they're waiting for a signal of some sort. There is a long network requests for an image during the print-preview operation, but that doesn't seem to start until ~30sec into the hang, so it might be involved but it isn't the full story...

This feels like it could be a delay with IPC messages or something along those lines... jwatt / BobOwen, do you have any ideas here?

The URL for the print preview/print was:
https://profiler.firefox.com/

Mike

No word... Wife just reminded me she's frustrated (tho she can eventually gain access to the internet via yahoo.com.) Just wondering...

I am seeing "30.2s Load 2147484104" in the profile Daniel posted in comment 8, which looks like loading an image took 30.2s. That sounds like bug 1686983.

See Also: → 1686983

Can this problem result from a combination of OS and Firefox print? If so, should I reset OS PRAM/NVPRAM on macbook and/or upgrade the OS (if I can?) I've done most of the other macbook and Firefox recommended fixes... Problem does not occur on my new Macbook Pro with same Firefox upgrade.

Our best theory so far is that this has to do with image-loads that are being triggered (or re-triggered) for the print-preview rendering, which are timing out or failing to load for some reason, as hiro noted in his reference to bug 1686983. (It's silly that this is blocking the Print Preview rendering, but it does for now; hopefully we'll address this in a patch for bug 1686983.)

So, sort-of answering your question: if the affected machine has any configuration or quirks that might cause network-requests to fail (e.g. maybe some proxy/VPN/filtering sort of software, or a slow/flaky WiFi antenna, etc), then that might be involved & be part of the explanation for why you're only seeing this on one machine but not the other.

Just for completeness sake. No VPN. Baud rate is most of the time near 300mbps. No filtering. Same TrendMicro AV. We use same wireless router. But we both have image loading problems. Many times a page with an image (or more than one image) will display grey blocks for the images. When I refresh the image that was grey is very often displayed. She most often still sees grey images after refreshing.
You'd think we had slightly different internal network cards/circuit boards. One that can handle 300 mbps and one that can't. Certainly not Apple.

Given the image-loading problems referenced in comment 14, I think that lends some credence to comment 13's theory here and mostly-confirms that this is a version of bug 1686983. Marking as such.

(I wonder what was [maybe still is?] causing the image loading problems; that would be interesting to investigate as well. But in the meantime, the print timing issues as a downstream effect of image-timeouts are essentially bug 1686983.)

Status: UNCONFIRMED → RESOLVED
Closed: 3 years ago
Duplicate of bug: 1686983
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.