Saturday, June 13, 2015

Chrome image onerror caused high CPU

We use lazy loading and onerror to handle image loading. However, the onerror fallback for a huge amount of images in DOM will cause Chrome high CPU. After pinpoint this logic, we suspect it is a Chrome rendering bug because same code works well on Firefox. Our solution is to remove the onerror fallback for list view with a lot of images.

No comments:

Post a Comment