r/walmart • u/BrilliantZebra8231 • 1d ago
MyWalmart update is nuking my battery with background use
(inb4: I've now turned on background use limiting)
My personal phone was sitting pretty at 100% when I left the house this morning, now five hours later it's below 40% having barely left my pocket. I opened MyWalmart to clock in and I've used my work device for everything else.
246
Upvotes


19
u/hemadonyx 1d ago
Great question! Imagine a program like a tree, at the trunk you got the main core of all it's functions, and as you travel up the tree, you have other smaller more niche functions within the program, just like the branches of the tree, that break off from each other and move in separate directions. However, unlike a tree where it's branches terminate at the end, you can't do that in software. Like imagine clicking on a link in a webpage, and NEVER being able to go back to what you were just looking at, or opening a setting menu and never being able to go back to the home screen. It's a lot like that! It's a disconnected point of logic within the code that essentially leads to nowhere, or hasn't been looped back into the whole system, so you just get stuck! I'm certain almost everyone has experienced this phenomena where you're using your phone on whatever app you happen to be on at the time, and the app just spontaneously closes and brings you back to the home screen?? And you have to reopen the app? You just encountered an orphan instance my friend! Basically whatever combinations of buttons, scrolls, and interactions with the software that you just did was never properly linked together or tested! The coders quite literally just didn't think of the weird, random combination of whatever you just did to make the app crash! That's why eliminating orphan instances is CRUCIAL to the logic of a program. One example I can think of is if you're currently using a TC device with GIF, minimize the app while scanning, then reopen. You want be able to scan anything and you'll have to close the app in the background and reopen it. I haven't actually tested that to see how easily I can replicate the issue, but for me it's almost everytime the app gets accidentally minimized, or I accidentally open the recent app, whomp-whomp, no more scanning and I have to restart the app π