[go: nahoru, domu]

Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Crashed: com.google.GDTFLLPrioritizer EXC_BAD_ACCESS KERN_INVALID_ADDRESS 0x0000000000000010 #4733

Closed
rahulOYO opened this issue Jan 23, 2020 · 9 comments

Comments

@rahulOYO
Copy link
rahulOYO commented Jan 23, 2020

[REQUIRED] Step 2: Describe your environment

Xcode version: 10.3
Firebase SDK version: 6.13.0
Firebase Component: (Core, Performance)
Here is the snapshot for all firebase related versions:

- Firebase/Core (6.13.0):
    - Firebase/CoreOnly
    - FirebaseAnalytics (= 6.1.6)
  - Firebase/CoreOnly (6.13.0):
    - FirebaseCore (= 6.4.0)
  - Firebase/Performance (6.13.0):
    - Firebase/CoreOnly
    - FirebasePerformance (~> 3.1.7)
  - FirebaseABTesting (3.1.2):
    - FirebaseAnalyticsInterop (~> 1.3)
    - FirebaseCore (~> 6.1)
    - Protobuf (>= 3.9.2, ~> 3.9)
  - FirebaseAnalytics (6.1.6):
    - FirebaseCore (~> 6.4)
    - FirebaseInstanceID (~> 4.2)
    - GoogleAppMeasurement (= 6.1.6)
    - GoogleUtilities/AppDelegateSwizzler (~> 6.0)
    - GoogleUtilities/MethodSwizzler (~> 6.0)
    - GoogleUtilities/Network (~> 6.0)
    - "GoogleUtilities/NSData+zlib (~> 6.0)"
    - nanopb (= 0.3.9011)
  - FirebaseAnalyticsInterop (1.4.0)
  - FirebaseCore (6.4.0):
    - FirebaseCoreDiagnostics (~> 1.0)
    - FirebaseCoreDiagnosticsInterop (~> 1.0)
    - GoogleUtilities/Environment (~> 6.2)
    - GoogleUtilities/Logger (~> 6.2)
  - FirebaseCoreDiagnostics (1.1.1):
    - FirebaseCoreDiagnosticsInterop (~> 1.0)
    - GoogleDataTransportCCTSupport (~> 1.0)
    - GoogleUtilities/Environment (~> 6.2)
    - GoogleUtilities/Logger (~> 6.2)
    - nanopb (~> 0.3.901)
  - FirebaseCoreDiagnosticsInterop (1.1.0)
  - FirebaseInstanceID (4.2.7):
    - FirebaseCore (~> 6.0)
    - GoogleUtilities/Environment (~> 6.0)
    - GoogleUtilities/UserDefaults (~> 6.0)
  - FirebasePerformance (3.1.7):
    - FirebaseCore (~> 6.4)
    - FirebaseInstanceID (~> 4.2)
    - FirebaseRemoteConfig (~> 4.4)
    - GoogleToolboxForMac/Logger (~> 2.1)
    - "GoogleToolboxForMac/NSData+zlib (~> 2.1)"
    - GoogleUtilities/Environment (~> 6.2)
    - GoogleUtilities/ISASwizzler (~> 6.2)
    - GoogleUtilities/MethodSwizzler (~> 6.2)
    - GTMSessionFetcher/Core (~> 1.1)
    - Protobuf (~> 3.9)
  - FirebaseRemoteConfig (4.4.5):
    - FirebaseABTesting (~> 3.1)
    - FirebaseAnalyticsInterop (~> 1.4)
    - FirebaseCore (~> 6.2)
    - FirebaseInstanceID (~> 4.2)
    - GoogleUtilities/Environment (~> 6.2)
    - "GoogleUtilities/NSData+zlib (~> 6.2)"
    - Protobuf (>= 3.9.2, ~> 3.9)

[REQUIRED] Step 3: Describe the problem

Steps to reproduce:

Although I can't reproduce the crash but I am getting a lot of crashes for my app on Crashlytics and those are in this queue only.

Stack trace of the GDTCCTUploader thread

Crashed: com.google.GDTCORUploadCoordinator
0  libobjc.A.dylib                0x1819eef70 objc_msgSend + 16
1  ???                            0x10c2a1c70 (Missing)
2  ???                            0x10c285dc8 (Missing)
3  CoreFoundation                 0x182ec1e94 CFTimeZoneCopySystem + 40
4  oyo-ios                        0x1010f7410 -[GDTCORClock init] + 86 (GDTCORClock.m:86)
5  oyo-ios                        0x1010f7470 +[GDTCORClock snapshot] + 94 (GDTCORClock.m:94)
6  oyo-ios                        0x1010f7494 +[GDTCORClock clockSnapshotInTheFuture:] + 99 (GDTCORClock.m:99)
7  oyo-ios                        0x1010fe36c -[GDTCORUploadPackage initWithTarget:] + 43 (GDTCORUploadPackage.m:43)
8  oyo-ios                        0x101101918 -[GDTFLLPrioritizer uploadPackageWithConditions:] + 61 (GDTFLLPrioritizer.m:61)
9  oyo-ios                        0x1010fd85c __52-[GDTCORUploadCoordinator uploadTargets:conditions:]_block_invoke + 118 (GDTCORUploadCoordinator.m:118)
10 libdispatch.dylib              0x181e2e1fc _dispatch_call_block_and_release + 24
11 libdispatch.dylib              0x181e2e1bc _dispatch_client_callout + 16
12 libdispatch.dylib              0x181e3c3dc _dispatch_queue_serial_drain + 928
13 libdispatch.dylib              0x181e319a4 _dispatch_queue_invoke + 652
14 libdispatch.dylib              0x181e3e34c _dispatch_root_queue_drain + 572
15 libdispatch.dylib              0x181e3e0ac _dispatch_worker_thread3 + 124
16 libsystem_pthread.dylib        0x1820372a0 _pthread_wqthread + 1288
17 libsystem_pthread.dylib        0x182036d8c start_wqthread + 4
@google-oss-bot
Copy link

I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight.

@rizafran
Copy link
Contributor

Hi @rahulOYO, I'm going to close this issue because I noticed that you filed another one on #4399 and the crash logs are similar. If you're still encountering the same issue, please reply on that issue to avoid confusion.

@rahulOYO
Copy link
Author
rahulOYO commented Jan 23, 2020

Thanks @rizafran ,

The crash log was copied by mistake.
I have updated the crash log. Can you please check and reopen the issue?

@visumickey
Copy link
Contributor

This does not seem to be an issue with Performance and seems different from the one mentioned (#4399). This issue seems to be arising out of GoogleDataTransport library. The issue mentions the crash is from FPREventsQueue thread, but the crashed thread is GDTCORUploadCoordinator. So re-opening this issue and assigning this to GoogleDataTransport.

@rahulOYO
Copy link
Author

Hi Team,

is there any update here?

@rizafran
Copy link
Contributor
rizafran commented Jan 29, 2020

Hi @rahulOYO, do you have a chance to test if the issue still happens using the latest GoogleDataTransportCCTSupport to 1.3.1, GoogleDataTransport(3.3.1) or update your SDK to the latest one?

@rahulOYO
Copy link
Author

Thanks. I will try updating the same

@rizafran
Copy link
Contributor

Hello @rahulOYO, may I know if you're still having issues here after updating to the latest version?

@rahulOYO
Copy link
Author

Thanks @rizafran Seems like it has been resolved now after updating the version.
Thanks for your support

@firebase firebase locked and limited conversation to collaborators Mar 13, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

5 participants