2044629 - Accepting the cookies on whereby.com causes the website to freeze

Status: RESOLVED DUPLICATE of bug 2042605

(Core :: JavaScript Engine, defect, P2)

Description

[Daniel Bodea [:danibodea]]

Attachment: website freese after cookies acceptance(2).gif

Note

• Accepting cookies on whereby.com causes the website to freese and the browser to slow down.

Found in

• Nightly v153.0a1

Affected versions

• Nightly v153.0a1

Tested platforms

• Affected platforms: MacOS 14 M1, Windows 10, MacOS26.5.1
• Unaffected platforms: -

Steps to reproduce

1. Load https://whereby.com/
2. Accept the website's cookies.

Expected result

• Website works correctly.

Actual result

• The websiute freezes, it is not responding to clicks; the browser is slowed down.

Regression range

• Potentially regressed by: bug 2027803

Comment 1

[BugBot [:suhaib / :marco]]

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

Comment 2

[Valentin Gosu [:valentin]]

I can't reproduce this, but this sounds like a JS issue, not necessarily a cookie issue.

Comment 3

[BugBot [:suhaib / :marco]]

:arai, since you are the author of the regressor, bug 2027803, could you take a look? Also, could you set the severity field?

For more information, please visit BugBot documentation.

Comment 4

[Tooru Fujisawa [:arai]]

It doesn't immediately reproduce, but
I see that https://snap.licdn.com/li.lms-analytics/insight.min.js is loaded multiple times there, which is almost same symptom as bug 2042605

edit: actually it reproduces for me.

Comment 5

[Tooru Fujisawa [:arai]]

Found the issue, described in bug 2042605 comment #18.

The gtm.js contains a minified+compiled code of the template which presumably provided by users.

The related code is the below.
https://github.com/linkedin/linkedin-gtm-community-template/blob/b27413acdce0edfd21b46e45f79b147f46c78cea/template.tpl#L210-L216
There was a fix for the condition to load the insight.min.js, from 3 years ago
https://github.com/linkedin/linkedin-gtm-community-template/commit/d6d31ee6f8880ffd8037e4aea7146ccd7cbba27b

But the whereby.com's gtm.js doesn't seem to have the fix applied:

                [50, "t", [46],
                    [22, ["n"],
                        [46, [53, [52, "u", ["i", "lintrk"]],
                            [52, "v", [8, "tmsource", "gtmv2"]],
                            [43, [15, "v"], "conversion_url", [15, "m"]],
                            [22, [1, [17, [15, "k"], "length"],
                                    [24, [17, [15, "k"], "length"], 3]
                                ],
                                [46, [2, [15, "k"], "forEach", [7, [51, "", [7, "w"],
                                    [43, [15, "v"], "conversion_id", [15, "w"]],
                                    ["u", "track", [15, "v"]]
                                ]]]],
                                [46, ["u", "track", [15, "v"]]]
                            ]
                        ]],
                        [46, ["f", "_already_called_lintrk", true, true],
                            ["h", "https://snap.licdn.com/li.lms-analytics/insight.min.js", [15, "q"],
                                [15, "r"]
                            ]
                        ]
                    ]
                ],