# Why is location plugin using so much CPU?

**URL:** https://meta.discourse.org/t/why-is-location-plugin-using-so-much-cpu/171478
**Category:** Self-hosting
**Created:** [November 27, 2020, 9:29am UTC](https://meta.discourse.org/t/why-is-location-plugin-using-so-much-cpu/171478 "2020-11-27T09:29:33Z")
**Posts on this page:** 1
**Showing post:** 6

<div class="post-metadata">

### Author: ![Richie](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/richie/32/115110_2.png) [@Richie](https://meta.discourse.org/u/Richie)
#### Post date: [November 27, 2020, 11:39am UTC](https://meta.discourse.org/t/why-is-location-plugin-using-so-much-cpu/171478/6 "2020-11-27T11:39:55Z")

</div>

Mine has also returned completely back to normal after turning off the locations plugin:

 ![image](https://global.discourse-cdn.com/meta/original/3X/d/8/d8ba5852690ea71735a258f6680ac81ac94483e9.png)

Did you have the issue I’ve mentioned in this topic too @ckshen ?

> [@Locations Plugin earth\_africa](https://meta.discourse.org/t/locations-plugin/69742/639):
>
> Latest update to core seems to have killed this stone dead: Clicking the user map, or the map icon on a user card causes a self inflicted dos pensive It then just keeps going, killing the browser stone dead within a handful of seconds: Same on the user map page: I’ve had to disable the plugin completely this morning.

---

_[View the full topic](https://meta.discourse.org/t/why-is-location-plugin-using-so-much-cpu/171478)._