Browser footprints when running notebooks - Chrome vs Firefox

We’re noticing feedback in a course forum that certain notebooks, particularly ones that work with reasonably sized in memory dataframes plotting OpenStreetMap (I think) maps using folium cause Chrome browser to just eat memory and CPU resource and hang the machine, whereas Firefox seems to work fine.

Anyone else noticed this / done comparisons on how well notebooks perform in Chrome vs Firefox?

Never seen anything like this, but anecdotally I feel that chrome hogs much more resources as well!