I am new to flutter. I have got error
"loading many images goes out of memory in flutter ios"
and I got message from debugger
"Terminated due to memory issue".
I have tryout all of image view - cache_image, progress_image, extended_image but still got same error so please if you have any idea about this and solution for this so help me. Thanks in advance!!
Screen shot of XCode console,
It is due to too much memory consumption, I got same error for my project as well but it was very difficult to find it, for me I was using a
ListView.builder
with
physics: NeverScrollableScrollPhysics(),
which load the whole data once and occupy memory, and for long list of data, I got same error. I hope this will help to find problem for this issue
Related
I'm having random crashes within my swift app and they are all throwing a similar error around CFDictionaryGetValue
Here are two screenshots from my Google Crashlytics showing the error and that its effecting to different URLs, Note these are from two separate crashes
Then here is also a screenshot directly from within Xcode where I was able to reproduct the error:
There doesn't seem to be any specific action that causes this issue and it occurs at random times.
And advise for trying to trace it and debug would be much appreciated!
Thanks
Oliver
As it turns out this issue was caused by a bug within the Firebase Performance SDK. After removing the SDK everything is working as expected
https://github.com/firebase/firebase-ios-sdk/issues/6734?fbclid=IwAR0L5U4dsBjyUGmklr8qEohlKTyY7P6zJwzWUnU3dUTnFmb0aclK4-rt5os
Try setting up an Exception breakpoint, it would probably give you more information to help you debug it:
In Xcode:
Go to Breakpoint Navigator (CMD+8)
Click the + button in the bottom left corner of the navigator and then choose Exception Breakpoint...
Select All in the Exception field
Re-run your app and you should get clearer information in the debugger
I've been working on an iOS app for the last 2 months and this morning suddenly the app started crashing when pressing the Map button to load the mapView.
Initially I thought maybe I caused it, but I went to an older build and the problem was still there.
Looking at the debugger:
MGLMapView WARNING UIViewController.automaticallyAdjustsScrollViewInsets is deprecated use MGLMapView.automaticallyAdjustContentInset instead.
libc++abi.dylib: terminating with uncaught exception of type std::domain_error
(lldb)
Can anyone shed any light on how to get past this? I keep thinking maybe mapbox changed something, or apple changed something, but somehow I don't think that's the case.
Any help is much appreciated.
Thanks.
So after following Magnas' post (thank you) and doing some more error log digging, found the issue!!!
Whilst loading the map viewer, I was parsing a json file for my markers to be displayed. Apparently one marker wasn't added properly in my SQL and it was crashing during parse.
After working just fine on both iPhone and iPad for a month, my Xcode 9 app has consistently started crashing causing me the following fatal problem: When I build & run it on an iPhone (simulator or device) Xcode completes loading the app and then crashes too fast for me to copy/paste the error from the debugger. When I run on iPad it works fine leading me to believe this is a result of something related to the split master/detail view.
If I use either an exception breakpoint or an "all C++ exceptions" it will stop at the AppDelegate class and crash if I hit play. If I use only an "all Objective-C exceptions" it will crash as before.
In the debug view hierarchy I get the following errors as well:
Error: Unable to capture view hierarchy.
Details: Log Title: Data source expression execution failure.
Log Details: error evaluating expression “(id)
[[(Class)objc_getClass("DBGTargetHub") sharedHub]
performRequestWithRequestInBase64:#"...
Log Method: -[DBGDataSourceConnectionLibViewDebugger
_executeLLDBExpression:forRequest:onPotentialThread:iteration:]
_block_invoke_2
Method: -[DBGViewDebugger updateDebugHierarchy]_block_invoke_2
I have tested other apps and this issue is unique to the app I am working on. Any ideas or debugging tips for how to proceed? I might just have to redo this whole project again if I can't even find the root cause of this! Appreciate any help.
Quick solution: Reset Simulator Device
I managed to resolve the above issue thanks to some serious digging. First, to resolve the instantaneous crash problem, I set a breakpoint at every line in the app delegate. That allowed me to narrow the error to a memory handling problem. From there I started running the code on one of each device available, and realized the crash only occurred on devices I had used earlier in development. Resetting those devices solved the problem.
The core issue here is that when you clean/rebuild your xcode program, it updates the app code on the device, but not necessarily the data model information. So when I changed my data model by including new data and renaming old data it was not properly updated.
Many crashes happened below the iOS9.3 (which means devices with iOS10 are OK)..
The crash logs seem to show that it's not a problem about API that can only be used below iOS 9.3 .
But I have no idea about the crash logs. ( I'm sorry ...for I just start to study iOS development for only 2 month )
Could you please help me analyze the crash logs ?
Really Thanks !
crash log 1
crash log 2
AXE_BAD_ACCESS - this is problem with memory. One of function tried to use variable which already released. I think you need to check use your TableView and cells for this table.
Also to find problem with memory you can try to use zombies
Used to have the similar strange crashes in my app. And only in production, when testing from TestFlight. Building on device with ios 9 caused no problems.
Maybe it sounds strange, but try to convert all images you use in app to images with included sRGB color profile. For me it helped.
My webview is getting stuck after 1 hour opened without use it, I'm getting the following errors:
Someone know what's the problem?
Thank you!
Carles
From the Log you can see that is a memory issue "Terminated due to memory issue"
It could be a memory leak or a “zombie” object.
Run the app with instruments to get more info and check if you have forgotten to disable zombies from the scheme editor , Memory Management options