The memory usage looks normal on my local machine, but CPU usage (about 60% on the mac) is a little bit high. Once I update `<select>` to `<div>`, the CPU usage becomes 30-40%. So this may be an issue which is specific to `<select>`. We run the infinite animations which updating its border's color (note: it's a main thread animation) on all elements. This may not be a common case. So mark this as S3 for now.
Bug 1832911 Comment 6 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
The memory usage looks normal on my local machine, but CPU usage (about 60% on the mac) is a little bit high. Once I update `<select>` to `<div>`, the CPU usage becomes 30-40%. So this may be an issue which is specific to `<select>`. (Or just because the `<div>` is too simple?) We run the infinite animations which updating its border's color (note: it's a main thread animation) on all elements. This may not be a common case. So mark this as S3 for now.
The memory usage looks normal on my local machine, but CPU usage (about 60% on the mac) is a little bit high. Once I update `<select>` to `<div>`, the CPU usage becomes 30-40%. So this may be an issue which is specific to `<select>`. (Or just because the `<div>` is just an empty block?) We run the infinite animations which updating its border's color (note: it's a main thread animation) on all elements. This may not be a common case. So mark this as S3 for now.