Bug: When trying to print certain messages, it takes a long time before the print dialogue box appears (if it appears at all)
Status: RESOLVED
Priority: --
Resolution: FIXED
Created: 2021-02-24 22:19:19+00:00
Resolved: 2021-04-22 12:24:32+00:00

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:87.0) Gecko/20100101 Firefox/87.0

Steps to reproduce:

I received two emails from a no-reply@i.vailresorts.com sender which is for ski lift tickets. I did a File > Print and also a CTRL-P  to print the tickets but it took in excess of 120 seconds before the print dialogue box appeared (if at all).  I tested with a few other emails (from eBay, Amazon, etc.) and the print dialogue box came up almost instantly.


Actual results:

When the print dialogue box did finally appear, error console shows this:

16:07:05.630
GEThttps://sr.rlcdn.com/465456.gif?s=20a78a53080adf4b49105c11177a49a7f9584ff2fedcace95bc41d7dab02cb00&n=1
[HTTP/2 200 OK 47ms]

16:07:05.637
GEThttps://sr.rlcdn.com/465456.gif?s=20a78a53080adf4b49105c11177a49a7f9584ff2fedcace95bc41d7dab02cb00&n=2
[HTTP/2 200 OK 57ms]

16:07:05.641
GEThttps://sr.rlcdn.com/465456.gif?s=20a78a53080adf4b49105c11177a49a7f9584ff2fedcace95bc41d7dab02cb00&n=3
[HTTP/2 200 OK 56ms]

16:07:05.644
GEThttps://sr.rlcdn.com/465456.gif?s=20a78a53080adf4b49105c11177a49a7f9584ff2fedcace95bc41d7dab02cb00&n=4
[HTTP/2 200 OK 56ms]

16:07:05.647
GEThttps://sr.rlcdn.com/465456.gif?s=20a78a53080adf4b49105c11177a49a7f9584ff2fedcace95bc41d7dab02cb00&n=5
[HTTP/2 200 OK 55ms]

16:07:05.649
GEThttps://t.myvisualiq.net/impression_pixel?r=1613428687&et=i&ago=212&ao=987&si=-11&ad=-11&sv1=-11&sz=7502&advt=11&chnl=-11&vndr=1144&u=EML_CNFDELIV_OTHR_000_WM_SR_00000_000000_TG0000_20210215_v00&pt=I
[HTTP/1.1 200 OK 115ms]

16:07:05.651
GEThttp://250analytics.vailresorts.com/ea/DKcE7fBHke/?e=<removed>@gmail.com

16:07:05.654
GEThttps://t.i.vailresorts.com/r/?id=h1b2d6e8,36c9875,1
[HTTP/1.1 200 OK 185ms]

and eventually ​followed by...

15:52:24.986 Uncaught (in promise) undefined msgPrintEngine.js:218:13

15:52:27.703 TypeError: browser is null BrowserElementParent.jsm:24:21
    receiveMessage resource://gre/actors/BrowserElementParent.jsm:24
    startPrint chrome://messenger/content/msgPrintEngine.js:218
    onStateChange chrome://messenger/content/msgPrintEngine.js:65
    startPrint chrome://messenger/content/msgPrintEngine.js:218
    onStateChange chrome://messenger/content/msgPrintEngine.js:65
    startPrint chrome://messenger/content/msgPrintEngine.js:218
    onStateChange chrome://messenger/content/msgPrintEngine.js:65
    startPrint chrome://messenger/content/msgPrintEngine.js:218
    onStateChange chrome://messenger/content/msgPrintEngine.js:65
    startPrint chrome://messenger/content/msgPrintEngine.js:218
    onStateChange chrome://messenger/content/msgPrintEngine.js:65
    startPrint chrome://messenger/content/msgPrintEngine.js:218
    onStateChange chrome://messenger/content/msgPrintEngine.js:65
    startPrint chrome://messenger/content/msgPrintEngine.js:218
    onStateChange chrome://messenger/content/msgPrintEngine.js:65
    startPrint chrome://messenger/content/msgPrintEngine.js:218
    onStateChange chrome://messenger/content/msgPrintEngine.js:65
    startPrint chrome://messenger/content/msgPrintEngine.js:218
    onStateChange chrome://messenger/content/msgPrintEngine.js:65
    startPrint chrome://messenger/content/msgPrintEngine.js:218
    onStateChange chrome://messenger/content/msgPrintEngine.js:65

15:52:42.973 Uncaught TypeError: window.opener is null msgPrintEngine.js:136:25
    InitPrintEngineWindow chrome://messenger/content/msgPrintEngine.js:136




Expected results:

Whether using File > Print or CTRL-P, it should come up withing a second or two.

Two things I want to add:

- When I click a different email and then click back to one of the problem emails, the status bar shows "Loading Message..." for about 35 seconds before it finishes. I did a profile of that and it's here: https://share.firefox.dev/3bAEJHV

- At the message bottom, it has 36 clickable links in the body. Shouldn't make difference but noting it in here in case it might be related and TB is getting stuck parsing those 36 links in order to print