We're digging into how to trim some more to make this less memory intensive.

It was talked about having some of you install a Memory Monitor-type app on your device so you can see just how much RAM you have, and how much of it is being used by all your other apps. It's not unheard of for a rogue app to be leaching your device's resources even though you don't have it running.

However, it seems Apple has truly made it difficult for thirdparty apps to see this data and report it back to you reliably (we tried 2 different apps and ran the scan at the same time and received 2 wildly different reports). Therefore I do not feel confident in recommending any specific app for you to use, because I have no idea how inaccurate it's response may be, and ultimately unhelpful to you in this situation.

Last night I tried numerous times to replicate what you all are describing on my iPod Touch. Granted it is newer than the iPhone 4 most of you are reportedly having the issues on, but in our initial Alpha testing my iPod was having trouble keeping up with the iPhones in regards to this similar issue. But I have not been able to create a crash on my device. It's frustrating, I know. It's more frustrating for us that we are unable to replicate this crash on any of our devices as well. The crash reports are all pointing to a lack of memory, but evidently all our test devices have plenty and therefore wont trigger a crash.

New version crashes on both my 4S and my iPad 2. Both are running iOS 7. Now I only have fuelly running on my 5S with iOS 8.

I have an iPhone 6 plus with 128mb of memory. Only using 1/2 of it and after the update i noticed a couple of things. My wife who uses Android uploaded a couple of fill ups on our trip and when I logged in, they did not show up. I logged out of my iPhone and logged back in. Upon logging back in, it immediately kicks out of the program. When I relaunch it, it says that I have no vehicles.

Now I have logged into the App from the internet and I can see my wife's fill-ups without issue but I still can't log into the app from my iPhone and see anything. Something broke in the last update. Needs to be fixed.

I have the same issue...iPhone 5s with iOS 7.1.2 and the GasTracker app launches, I see a white splash screen that is too large for my screen, no "OK" button to click and after a few seconds it disappears...if I double click the home button I see it is still running, I can select it but it will disappear a few seconds later. I restarted my phone, same issue. Deleted GasTracker and reloaded it from the AppStore...same issue.

Exact same issue with my iPhone 5s with iOS 7.1.2 :mad:

New version released today but nothing has changed - still crashes and leaves that white screen open with the update info. Another untested release :(
Iphone4. iOS 7

While it could very well be a ram issue, the common denominator seems to be ios 7.

Rebooted my iPhone 4 running iOS 7 and with no apps running tried opening Gas Tracker and same results - crash with the white info screen left open.
Here's the beginning of the crash log. Let me know if you want me to e-mail the entire log.

{"name":"GasTracker","bug_type":"109","os_version" :"iPhone OS 7.1.2 (11D257)","bundleID":"com.s2it.GasTracker","versio n":"3.0.2.11 (3.0.2)","app_name":"GasTracker"}
Incident Identifier: E14AE85C-9688-4D7D-B318-7D71DC717D68
CrashReporter Key: 9d4b5284ff8ed1693e3a2dee0dc431baa8b14d79
Hardware Model: iPhone3,1
Process: GasTracker [339]
Path: /var/mobile/Applications/6676C82F-98E9-4AB4-AF01-FDE731D27F40/GasTracker.app/GasTracker
Identifier: com.s2it.GasTracker
Version: 3.0.2.11 (3.0.2)
Code Type: ARM (Native)
Parent Process: launchd [1]

Date/Time: 2015-09-22 10:19:31.286 -0700
OS Version: iOS 7.1.2 (11D257)
Report Version: 104

Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Triggered by Thread: 0

I have a 4s with iOS7. Crashes every time.

Also, it appears to have dropped the last fuel up I had before the update.

That's simply not true.
As for the What's New screen, we simply cannot figure out why it's acting odd for some of you.
Indeed. We're still digging into this.