(In reply to Matthew Gaudet (he/him) [:mgaudet] from comment #3) > (Myself, I can't reproduce, but my machine is very fast) FWIW I reported this from a pretty fast machine as well; it's my main development machine, which is a ThinkPad P15 Gen 1. (In reply to Daniel Holbert [:dholbert] from comment #0) > STR: > 1. Log in to a twitter account > 2. Visit https://twitter.com/settings/your_twitter_data/twitter_interests > (Note: for me, this^ page has ~hundreds of entries; not sure how many are required to trigger the perf issue here, but I suspect you need lots.) To fill in the "how many entries" detail here, since that's probably relevant for how-bad-this-gets: it looks like I currently have 654 "interests" listed here. I got that number by inspecting one of my interests in devtools, and then selecting its parent (an unstyled `<div>`), and then evaluating `$0.childElementCount` in my web console.
Bug 1769131 Comment 4 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
(In reply to Matthew Gaudet (he/him) [:mgaudet] from comment #3) > (Myself, I can't reproduce, but my machine is very fast) FWIW I reported this from a pretty fast machine as well; it's my main development machine, which is a ThinkPad P15 Gen 1. (In reply to Daniel Holbert [:dholbert] from comment #0) > STR: > 1. Log in to a twitter account > 2. Visit https://twitter.com/settings/your_twitter_data/twitter_interests > (Note: for me, this^ page has ~hundreds of entries; not sure how many are required to trigger the perf issue here, but I suspect you need lots.) To fill in the "how many entries" detail here, since that's probably relevant for how-expensive-this-operation-is: it looks like I currently have 654 "interests" listed here. I got that number by inspecting one of my interests in devtools, and then selecting its parent (an unstyled `<div>`), and then evaluating `$0.childElementCount` in my web console.
(In reply to Matthew Gaudet (he/him) [:mgaudet] from comment #3) > (Myself, I can't reproduce, but my machine is very fast) FWIW I reported this from a pretty fast machine as well; it's my main development machine, which is a ThinkPad P15 Gen 1, purchased about a year ago. (In reply to Daniel Holbert [:dholbert] from comment #0) > STR: > 1. Log in to a twitter account > 2. Visit https://twitter.com/settings/your_twitter_data/twitter_interests > (Note: for me, this^ page has ~hundreds of entries; not sure how many are required to trigger the perf issue here, but I suspect you need lots.) To fill in the "how many entries" detail here, since that's probably relevant for how-expensive-this-operation-is: it looks like I currently have 654 "interests" listed here. I got that number by inspecting one of my interests in devtools, and then selecting its parent (an unstyled `<div>`), and then evaluating `$0.childElementCount` in my web console.