# Logo in corner - bug

**URL:** https://community.gemsofwar.com/t/logo-in-corner-bug/86337
**Category:** Bug Reports
**Created:** [November 4, 2024, 8:01pm UTC](https://community.gemsofwar.com/t/logo-in-corner-bug/86337 "2024-11-04T20:01:24Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![Zuul-Emo](https://avatars.discourse-cdn.com/v4/letter/z/67e7ee/32.png) [@Zuul-Emo](https://community.gemsofwar.com/u/Zuul-Emo)
#### Post date: [November 4, 2024, 8:01pm UTC](https://community.gemsofwar.com/t/logo-in-corner-bug/86337/1 "2024-11-04T20:01:24Z")

</div>

**Platform, device version and operating system:**  
PS5

**What you were expecting to happen, and what actually happened:**  
Playstation store icon stuck in bottom corner, when on map screen. Won’t go away. Guildmates have same issue.

**How often does this happen? When did it begin happening?**  
Since weekly reset.

**Steps to make it happen again**  
Turn on game.

---

<div class="post-metadata">

### Author: ![Valardolahaeris](https://avatars.discourse-cdn.com/v4/letter/v/e47774/32.png) [@Valardolahaeris](https://community.gemsofwar.com/u/Valardolahaeris)
#### Post date: [November 4, 2024, 8:56pm UTC](https://community.gemsofwar.com/t/logo-in-corner-bug/86337/2 "2024-11-04T20:56:39Z")

</div>

. A work around for this:  
When you get the cliffy error, dont click on the restart game button in game. Instead, Manually shut the game down by accessing the quick menu on your playstation and close application. This at least eliminates it until you get the next cliffy error.

---

<div class="post-metadata">

### Author: ![covertmuffin123](https://avatars.discourse-cdn.com/v4/letter/c/5daacb/32.png) [@covertmuffin123](https://community.gemsofwar.com/u/covertmuffin123)
#### Post date: [November 4, 2024, 9:38pm UTC](https://community.gemsofwar.com/t/logo-in-corner-bug/86337/3 "2024-11-04T21:38:03Z")

</div>

This was happening to me (PS4) and I got an overheating error/console crash. Console was not hot. It could be a coincidence, but it’s a sign of a memory leak or other poor optimization. If no one else reports it, feel free to ignore this.
