FOLLOW US

Our HTC 10 has a strange memory leak bug

Thomas Wellburn
May 5, 2016

We’re enjoying the HTC 10 a lot as it’s a great device with plenty of positives – the audio quality being a huge plus, but a certain bug has got us very confused.

I’ve been using the HTC 10 extensively for a few weeks while I gather my thoughts into a rather thorough review and have very little bad things to say about it… Except the memory leak. As a matter of fact, the bug has become so extreme that it’s actually affected my ability to review the device, such is the severity of the problem.

It all started out of the blue about a week ago when I tried to install a popular benchmarking application, only to be greeted with a ‘memory full’ popup out of nowhere. Confused as to why this is, I went into my Phone Storage setting and saw that the system memory had expanded to over 20GB. Various attempts at using cleaning apps could not fix the error, as they deal primarily with cached data and not system files. Hence, the only option was a drastic hard reset which wiped my handset back to factory settings.

htc 19

Whether this is a specific error with our HTC 10 or an application bug that is causing the system folder to swell remains to be seen, but this has not been a one-off occurrence. Just yesterday after HTC released their massive update, I noticed that the storage space had shrank considerably. Opening the settings and heading to Storage again revealed a similar story, the System folder has once again swelled past 20GB.

As I write this, I’m about to do my second factory reset, hoping that the patch HTC released has remedied the issue. The thing with memory leaking issues such as this is that they happen quietly in the background over a period of time. Trying to find out the cause requires almost constant monitoring of the Storage, which is pretty damn tedious. Hopefully the issue is sorted out but if it’s not, expect to hear something again from ourselves soon.

We reached out to HTC’s PR team for comment who swiftly said they were contacting the team to figure out the problem. We’ll keep you posted.

*EDIT: Turns out the issue was caused by a rogue application. We’ve written an additional piece on the issue that can be found here.

For more news, visit What Mobile’s dedicated news page.  

About the Author

Share this article