objc_object::release() - Selector name found in current argument registers: setLoadedAd:

Solar2D iOS
#1

Hello,

I am getting HockeyApp Crash reports but I have no idea what is the problem, could someone please help to identify what is happening.

There are lots of reports like this but I have no idea about the error.

Game is on the market right now but we have not started excessive marketing yet.

Thanks in advance,

bulupe

Here is the HockeyApp Report Detail;

Incident Identifier: *******************

CrashReporter Key: *******************
Hardware Model: iPhone7,1
Process: Scale [8132]
Path: /var/containers/Bundle/Application/DAAE1E38-0A10-4096-BB49-3733E71FCE0A/*******************
Identifier: com.*******************
Version: 2.3.1 (2017.03.152344)
Code Type: ARM-64
Parent Process: ??? [1]

Date/Time: 2017-03-15T20:56:55Z
Launch Time: 2017-03-15T20:53:34Z
OS Version: iPhone OS 10.2.1 (14D27)
Report Version: 104

Exception Type: SIGSEGV
Exception Codes: SEGV_ACCERR at 0x81b5ebec8
Crashed Thread: 0

Application Specific Information:
Selector name found in current argument registers: setLoadedAd:

#2

Hi,

I got Xcode crash reports too but still have no idea what is this related to, could anyone help me please.

Thank you

Bulent

#3

It might be worth filling a bug report.

As for what the error means

"This is an error that I have mostly seen on 64 bit iOS devices and can happen if multiple threads read and change a variable under ARC. For example, I fixed a crash today where multiple background threads were reading and using a static NSDate and NSString variable and updating them without doing any kind of locking or queueing.

Using core data objects on multiple threads can also cause this crash, as I have seen many times in my crash logs."

 

source: "http://stackoverflow.com/questions/19119943/what-does-segv-accerr-mean"

 

Please post build settings as well. It may be a plugin (hopefully non of mine)

#4

Hi Scott, 

Thanks for reply, looking at the analytics data it seems to have no effect on users but I am still worried. I guess it might be related to Applovin or Admob plugins I am using. Here is the build settings;

settings = { splashScreen = { ios = { enable = true, image = "scl\_splash.png" }, android = { enable = true, image = "scl\_splash.png" } }, orientation = { default = "portrait", supported = { "portrait", } }, -- -- iOS Section -- iphone = { iCloud = true, plist = { CFBundleShortVersionString = "2.3.2", MinimumOSVersion = "7.0", ITSAppUsesNonExemptEncryption = false, UIStatusBarHidden = false, UIPrerenderedIcon = true, UILaunchStoryboardName = 'launchscreen', UIBackgroundModes = {'remote-notification'}, UIApplicationExitsOnSuspend = false, CFBundleDisplayName = "\*\*\*\*\*", CFBundleName = "\*\*\*\*\*", CFBundleIconFiles = { "Icon.png", "Icon@2x.png", "Icon-60.png", "Icon-60@2x.png", "Icon-60@3x.png", "Icon-72.png", "Icon-72@2x.png", "Icon-76.png", "Icon-76@2x.png", "Icon-167.png", "Icon-Small-40.png", "Icon-Small-40@2x.png", "Icon-Small-50.png", "Icon-Small-50@2x.png", "Icon-Small.png", "Icon-Small@2x.png", "Icon-Small@3x.png" }, UIBackgroundModes = {"remote-notification"}, UILaunchImages = { { -- iPhone 4 Portrait ["UILaunchImageMinimumOSVersion"] = "7.0", ["UILaunchImageName"] = "Default", ["UILaunchImageOrientation"] = "Portrait", ["UILaunchImageSize"] = "{320, 480}" }, { -- iPhone 5 Portrait ["UILaunchImageMinimumOSVersion"] = "7.0", ["UILaunchImageName"] = "Default-568h", ["UILaunchImageOrientation"] = "Portrait", ["UILaunchImageSize"] = "{320, 568}" }, { -- iPad Portrait ["UILaunchImageMinimumOSVersion"] = "7.0", ["UILaunchImageName"] = "Default-Portrait", ["UILaunchImageOrientation"] = "Portrait", ["UILaunchImageSize"] = "{768, 1024}" }, { -- iPhone 6 Portrait ["UILaunchImageMinimumOSVersion"] = "8.0", ["UILaunchImageName"] = "Default-667h", ["UILaunchImageOrientation"] = "Portrait", ["UILaunchImageSize"] = "{375, 667}" }, { -- iPhone 6 Plus Portrait ["UILaunchImageMinimumOSVersion"] = "8.0", ["UILaunchImageName"] = "Default-736h", ["UILaunchImageOrientation"] = "Portrait", ["UILaunchImageSize"] = "{414, 736}" }, { -- iPad Pro Portrait ["UILaunchImageMinimumOSVersion"] = "9.0", ["UILaunchImageName"] = "Default-Portrait-1366", ["UILaunchImageOrientation"] = "Portrait", ["UILaunchImageSize"] = "{1024, 1366}" }, }, NSAppTransportSecurity = { NSAllowsArbitraryLoads=true, NSExceptionDomains = { ["\*\*\*\*\*\*\*\*"] = { NSIncludesSubdomains = true, NSThirdPartyExceptionAllowsInsecureHTTPLoads = true, }, ["192.168.56.101"] = { NSIncludesSubdomains = true, NSThirdPartyExceptionAllowsInsecureHTTPLoads = true, }, } }, NSCalendarsUsageDescription = "No need for calendar.", NSPhotoLibraryUsageDescription = "This app would like to save screenshots.", NSCameraUsageDescription = "No need for camera.", FacebookAppID = "\*\*\*\*\*\*\*\*\*\*\*", CFBundleURLTypes = { { CFBundleURLSchemes = { "\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*", } } }, LSApplicationQueriesSchemes = { "fb", "fbapi", "fbauth2", "fb-messenger-api", "fbshareextension" }, }, }, -- -- Android Section -- android = { usesPermissions = { "android.permission.INTERNET", }, facebookAppId = "\*\*\*\*\*\*\*\*\*\*\*\*\*" }, -- Plugins Section plugins = { ["plugin.applovin"] = { publisherId = "com.coronalabs" }, ["plugin.admob"] = { publisherId = "com.coronalabs" }, ["plugin.math2d"] = { publisherId = "com.roaminggamer" }, ["plugin.hockey"] = { publisherId = "com.coronalabs" }, ["plugin.openudid"] = { publisherId = "com.coronalabs", supportedPlatforms = { iphone=true }, }, ["plugin.googleAnalytics"] = { publisherId = "com.coronalabs" }, ["plugin.iCloud"] = { publisherId = "com.coronalabs" }, ["plugin.facebook.v4"] = { publisherId = "com.coronalabs" }, ["CoronaProvider.native.popup.social"] = { publisherId = "com.coronalabs" }, ["CoronaProvider.native.popup.activity"] = { publisherId = "com.coronalabs", supportedPlatforms = { iphone=true } }, }, }
#5

It could be anything. The error logs are a little unhelpful( at least to me). There is a chance a person with a jail broken device or other 3rd party software is running on the phone. On my phone I have 8 apps not though the App Store.

#6

If is around 1% percent of your customers, I would not be worried.

#7

No actually devices are not jail broken according to HockeyApp and unfortunately its effecting quite big portion of users. However it seems not to have any visible effect on user behaviour perhaps it is handled silently.

I really have to find this out and solve. I wish I could replicate this error but not a chance so far.

I will release a new version and try to find the problem by uploading dsym although I could not manage to make it work so far with test versions on HockeyApp.

Any help would be appreciated.

Thank you

Bulent

#8

Bulent any luck?

I am having the same issue. 222 “crashes today” but nobody has sent me a support ticket about it. So maybe it is nothing to worry about.

#9

nope, still getting these crash reports and still no user saying app is crashing. But it is really annoying, I wish I could have find what it is!

#10

A SIGSEGV is known as a “Segment Violation”. This is where your app is trying to access some memory it doesn’t have the rights/privileges to. I don’t know if HockeyApp’s crash handling has a way to prevent this, but usually a SIGSEGV is force exited by the operating system.

We would like to think that our code is pretty hardened to avoid segment violations. But there are a few things you can do that will create them. Also I cannot speak for plugins, though the ones we write have a good amount of testing on them.

Where to look? This can happen if you try to access a chunk of memory that has been freed already and the pointer to the memory is invalid. It can also happen trying to execute code that’s been removed from memory as well.  When I’ve experienced this in the past, it’s almost always due to a timer or enterFrame listener still running in a scene and I remove that scene from memory. The timer and enterFrame listener’s don’t get removed and they try to call a function that no longer exists and your app crashes.

Also sounds and transitions that have onComplete listeners (well really any Callback function) maybe guilty of this as well when they try to call that function and it’s been removed from memory.  

Look through those scenarios and see if those could be triggering your issue. If it’s happening with the frequency you say it is, you should be able to find it with local testing. Maybe try turning off the Hockey crash catching and see if you start getting local crashes. It might also help for you to completely remove the app from your test device and install it fresh (either through Apple’s TestFlight or Google’s Alpha/Beta release channels) so you’re getting the user experience, not a testing experience.

Rob

#11

Hi Rob,

Thank you for detailed answer. Unfortunately we are not able to detect this error on our tests and as we are seeing  setLoadedAd  we are suspecting on ads plugins, I think it might be related to something when you quit app while an interstitial or video ad is being played. I will try to figure out this by turning of HockeyApp.

Thank you

Bulent

#12

Hi again,

I’ve got some extra details about this error. Now I am almost sure this is related to applovin plugin because there is a very serious correlation between interstitial banner impressions and daily crash reports. We were trying to find optimal number of interstitial ads to be shown and thats when we found .

Is there any chance somebody can help us to find the problem?

Bulent

#13

You beat me to it. I removed the applovin plugin from the latest build. The error and crashes are gone. Back to Admob only ads until the issue is resolved.

#14

For us it is not an option to remove applovin plugin so I am still trying to find out when it happens. So far we are almost sure this is not something users see and I am suspecting it happens when users try to close application when an interstitial is playing.

#15

We have a new version of the Applovin plugin in the pipeline where this bug will be fixed.

#16

Any chance you will remove the external read permision on the android version? it will make me very happy.

Adrian

#17

We never specifically include the Android READ permission in any of our plugins.

We do include the WRITE permission as ad networks that provide video ads need this permission to provide full functionality when loading interstitial video/rewarded video ads. Without the WRITE permission the functionality of video ads will be hampered and will affect the type of ads that will be displayed, and ultimately reduce ad revenue.

#18

Yes. I understand why to include the Write permission. And yes I understand that that is what is stated in the documentation.

But just an empty project on Android with just Applovin ends up with the read permission of external storage. You can check it by going to the permission section of the app. In any case, I received so many complaints I had to remove the plugin (that and the fantom crashes).

#19

The WRITE permission results in an implicit READ in the Google Play Console, so it’s not possible to just remove the READ permission.

It’s a bit of a catch 22 situation. Without WRITE the implicit READ will be gone from the Google Play Console, however the absence of WRITE will also prevent all types of video ads from performing well which will negatively affect ad revenue.

#20

Thank you for explaining it.