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 on [FPRConfigurations hasRemoteConfigFetchHappened] + 491012 #4207

Closed
PradeshKumar88 opened this issue Oct 31, 2019 · 8 comments
Assignees
Milestone

Comments

@PradeshKumar88
Copy link

@PradeshKumar88 PradeshKumar88 commented Oct 31, 2019

Crash reported by Crashlytics:

iOS 12.4.2 (16G114)
iPad Mini 2

Crashed: com.google.perf.FPREventsQueue
EXC_BAD_ACCESS KERN_INVALID_ADDRESS 0x0000000f3522a3c0

Stack Trace 1:

Crashed: com.google.perf.FPREventsQueue
0  libobjc.A.dylib                0x1b0edaca8 objc_release + 24
1  PO3-Residential                0x100d66ad4 -[FPRConfigurations hasRemoteConfigFetchHappened] + 491012
2  PO3-Residential                0x100d66f10 -[FPRConfigurations sdkEnabled] + 492096
3  PO3-Residential                0x100d6b6c0 -[FPRClient processAndLogEvent:] + 510448
4  PO3-Residential                0x100d6afc0 __22-[FPRClient logTrace:]_block_invoke + 508656
5  libdispatch.dylib              0x1b1727a38 _dispatch_call_block_and_release + 24
6  libdispatch.dylib              0x1b17287d4 _dispatch_client_callout + 16
7  libdispatch.dylib              0x1b16d1454 _dispatch_lane_serial_drain$VARIANT$mp + 896
8  libdispatch.dylib              0x1b16d1e40 _dispatch_lane_invoke$VARIANT$mp + 428
9  libdispatch.dylib              0x1b16da4ac _dispatch_workloop_worker_thread + 596
10 libsystem_pthread.dylib        0x1b1909114 _pthread_wqthread + 304
11 libsystem_pthread.dylib        0x1b190bcd4 start_wqthread + 4
@google-oss-bot

This comment was marked as resolved.

Copy link

@google-oss-bot google-oss-bot commented Oct 31, 2019

I found a few problems with this issue:

  • I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight.
  • This issue does not seem to follow the issue template. Make sure you provide all the required information.
@skuske

This comment has been minimized.

Copy link

@skuske skuske commented Oct 31, 2019

We are seeing a similar issue, but pretty rare:

Crashed: CCTLogWriter
EXC_BAD_ACCESS KERN_INVALID_ADDRESS 0x00000008785c7e70
-[FPRConfigurations hasRemoteConfigFetchHappened]
Crashed: CCTLogWriter
0  libobjc.A.dylib                0x1f4666ca8 objc_release + 24
1  AppName                        0x10479442c -[FPRConfigurations hasRemoteConfigFetchHappened]
2  AppName                        0x104794c8c -[FPRConfigurations logTraceSamplingRateForLogSource:]
3  AppName                        0x1047908ec -[FPRLogSampler shouldSampleForLogSource:event:]
4  AppName                        0x104790804 -[FPRLogSampler transform:]
5  AppName                        0x1047e0980 -[CCTLogWriter writeLogInternal:pseudonymousID:logDirectory:clock:logTransformers:]
6  AppName                        0x1047e02f4 __75-[CCTLogWriter writeLog:pseudonymousID:logDirectory:clock:logTransformers:]_block_invoke_2
7  libdispatch.dylib              0x1f4eb3a38 _dispatch_call_block_and_release + 24
8  libdispatch.dylib              0x1f4eb47d4 _dispatch_client_callout + 16
9  libdispatch.dylib              0x1f4e5d324 _dispatch_lane_serial_drain$VARIANT$mp + 592
10 libdispatch.dylib              0x1f4e5de40 _dispatch_lane_invoke$VARIANT$mp + 428
11 libdispatch.dylib              0x1f4e664ac _dispatch_workloop_worker_thread + 596
12 libsystem_pthread.dylib        0x1f5095114 _pthread_wqthread + 304
13 libsystem_pthread.dylib        0x1f5097cd4 start_wqthread + 4
@kennic

This comment has been minimized.

Copy link

@kennic kennic commented Nov 6, 2019

We have the same issue that causes our Crash-free value dropping, please fix.

@dongshuju

This comment has been minimized.

Copy link

@dongshuju dongshuju commented Nov 11, 2019

We have same issue, here is the crash log:

#0Crashed: com.google.perf.FPREventsQueueEXC_BAD_ACCESS KERN_INVALID_ADDRESS 0x00000005ef18da60 Raw Text

0 | libobjc.A.dylib | objc_release + 28
1 | ** | -[FPRConfigurations hasRemoteConfigFetchHappened] + 4344579196
2 | ** | -[FPRConfigurations sdkEnabled] + 4344580280
3 | ** | -[FPRClient processAndLogEvent:] + 4344598620
4 | ** | __22-[FPRClient logTrace:]_block_invoke + 4344596832
5 | libdispatch.dylib | + 32
11 | libsystem_pthread.dylib | start_wqthread + 4

@skuske

This comment has been minimized.

Copy link

@skuske skuske commented Nov 11, 2019

We removed the Performance APIs from our app as we did not know how to fix the issue other ways. 11 days without any possible solution is way too much time.

@Vinzius

This comment has been minimized.

Copy link

@Vinzius Vinzius commented Nov 13, 2019

Same problem here.

@visumickey

This comment has been minimized.

Copy link

@visumickey visumickey commented Nov 13, 2019

This issue is fixed and will be rolled out in the upcoming release of Firebase Performance.

@visumickey visumickey added this to the M60 milestone Nov 13, 2019
@ryanwilson

This comment has been minimized.

Copy link
Member

@ryanwilson ryanwilson commented Nov 14, 2019

Firebase 6.13.0 was just released and should address this issue. Please update and re-open if you're still seeing the issue, thanks!

@ryanwilson ryanwilson closed this Nov 14, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
9 participants
You can’t perform that action at this time.