Hey there! Really sorry to hear about this. We've put in a lot of focus to minimize the eesel footprint on your CPU so in theory you shouldn't have experienced that (and we're keen to fix this!).

Did it happen right after install of eesel in particular?