Scribd
Upload
3 views4 pages

Facebook App Error Logs Summary

Uploaded by

asdentjuwita
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
3 views4 pages

Facebook App Error Logs Summary

Uploaded by

asdentjuwita
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd

09-28 22:39:14.

485 912 912 E wificond: vivo add tx_good 21796 tx_bad 1 rx_good
49083 tx_retry 766
09-28 23:21:11.271 912 912 E wificond: vivo add tx_good 31796 tx_bad 0 rx_good
26390 tx_retry 2193
09-29 11:34:03.552 1313 29177 E ActivityManager: 48% 1796/[Link]:
37% user + 10% kernel / faults: 19102 minor
09-29 12:33:25.985 1313 10418 E ActivityManager: 42% 1796/[Link]:
33% user + 8.8% kernel / faults: 32611 minor 5 major
09-29 12:34:57.365 912 912 E wificond: vivo add tx_good 20719 tx_bad 4 rx_good
26697 tx_retry 17962
09-29 12:35:00.388 912 912 E wificond: vivo add tx_good 20722 tx_bad 4 rx_good
26711 tx_retry 17962
09-29 12:35:03.400 912 912 E wificond: vivo add tx_good 20724 tx_bad 4 rx_good
26725 tx_retry 17967
09-29 12:35:06.429 912 912 E wificond: vivo add tx_good 20730 tx_bad 4 rx_good
26737 tx_retry 17967
09-29 12:35:09.456 912 912 E wificond: vivo add tx_good 20730 tx_bad 4 rx_good
26745 tx_retry 17967
09-29 12:35:12.489 912 912 E wificond: vivo add tx_good 20733 tx_bad 4 rx_good
26762 tx_retry 17967
09-29 12:56:39.525 1313 16593 E ActivityManager: 49% 1796/[Link]:
40% user + 8.6% kernel / faults: 3588 minor
09-29 14:23:58.533 1313 23682 E ActivityManager: 72% 1796/[Link]:
60% user + 12% kernel / faults: 10121 minor
09-29 15:06:40.744 1313 7622 E ActivityManager: 48% 1796/[Link]:
42% user + 6.7% kernel / faults: 5670 minor
09-29 16:18:01.047 17964 17964 E _V_ANRManager: mPackageName = [Link],
Get anr service = [Link]$Stub$Proxy@768f040
09-29 16:21:35.949 1313 1338 E _V_VivoVibratorServiceImpl: onProcessDied pid:
17964,uid: 10075
09-29 16:56:39.436 1313 25958 E ActivityManager: 112% 1796/[Link]:
96% user + 15% kernel / faults: 143168 minor 241 major
09-29 17:28:06.687 1313 29453 E ActivityManager: 74% 1796/[Link]:
62% user + 11% kernel / faults: 112569 minor
09-29 17:41:54.871 912 912 E wificond: vivo add tx_good 241796 tx_bad 2 rx_good
318064 tx_retry 39606
09-29 17:51:50.323 912 912 E wificond: vivo add tx_good 401894 tx_bad 2 rx_good
517960 tx_retry 40742
09-29 18:00:26.700 518 1627 V APM_AudioPolicyManager: setOutputDevices()
AF::createAudioPatch returned 0 patchHandle 1796 num_sources 1 num_sinks 1
09-29 18:01:56.707 1796 1796 E [Link]: 0ms: LollipopUploadService
instantiating…
09-29 18:01:56.708 1796 1796 E [Link]: Main thread was blocked for
34ms in the background starting with LollipopUploadService
09-29 18:04:19.434 917 982 E [Link]@2.0-service-mediatek:
akm_log setv_mag(uT) 84.300003, 39.600002, -103.950005 ts 71117966372
09-29 18:07:28.632 1796 1796 E [Link]: 0ms:
ConditionalWorkerService instantiating…
09-29 18:07:28.635 1796 1796 E [Link]: Main thread was blocked for
297ms in the background starting with ConditionalWorkerService
09-29 18:07:30.279 1796 1796 E [Link]: 0ms: BlueService
instantiating…
09-29 18:07:30.280 1796 1796 E [Link]: Main thread was blocked for
39ms in the background starting with BlueService
09-29 18:07:30.523 1796 31906 E fb4a.9Px: Failure decoding override info
09-29 18:07:30.523 1796 31906 E fb4a.9Px: X.9Pz: [Link]: No value
for new_locale
09-29 18:07:30.523 1796 31906 E fb4a.9Px: at X.9Py.<init>(:116)
09-29 18:07:30.523 1796 31906 E fb4a.9Px: at [Link](:52)
09-29 18:07:30.523 1796 31906 E fb4a.9Px: at [Link](:104)
09-29 18:07:30.523 1796 31906 E fb4a.9Px: at
[Link]([Link])
09-29 18:07:30.523 1796 31906 E fb4a.9Px: at [Link](:54)
09-29 18:07:30.523 1796 31906 E fb4a.9Px: at
[Link]([Link])
09-29 18:07:30.523 1796 31906 E fb4a.9Px: at
[Link]$[Link]([Link])
09-29 18:07:30.523 1796 31906 E fb4a.9Px: at [Link](:3)
09-29 18:07:30.523 1796 31906 E fb4a.9Px: at [Link](:17)
09-29 18:07:30.523 1796 31906 E fb4a.9Px: at
[Link]([Link])
09-29 18:07:30.523 1796 31906 E fb4a.9Px: Caused by: [Link]: No
value for new_locale
09-29 18:07:30.523 1796 31906 E fb4a.9Px: at
[Link]([Link])
09-29 18:07:30.523 1796 31906 E fb4a.9Px: at
[Link]([Link])
09-29 18:07:30.523 1796 31906 E fb4a.9Px: at X.9Py.<init>(:11)
09-29 18:07:30.523 1796 31906 E fb4a.9Px: ... 9 more
09-29 18:08:19.317 1796 1796 E [Link]: 0ms:
FacebookPushServerFinishNotifiedLollipopService instantiating…
09-29 18:08:19.318 1796 1796 E [Link]: Main thread was blocked for
38ms in the background starting with
FacebookPushServerFinishNotifiedLollipopService
09-29 18:14:34.874 1796 1796 E [Link]: Redirecting MSYS Execution
scheduling from the UI thread to a custom executor
09-29 18:14:34.886 1796 2242 E [Link]: E[N data-
request]_HandleDataResponse(1951)=>Data request error for task 6BF45ED8-A595-4A65-
A8BA-9CCEA7243387 (response type 1): (null)
09-29 18:14:34.889 1796 2242 E [Link]: E[N data-
request]_HandleDataResponse(1951)=>Data request error for task 9F080980-59F4-460F-
94B7-8AD6A2F3EA5A (response type 1): (null)
09-29 18:14:34.893 1796 2733 E [Link]: E[S
task_queue_handling]MCDLightSpeedTaskExecutorNetworkCompletionCallback(1131)=>Handl
ing send error for taskId=8252 batchSize=1 queue=acs_sync_LS_MediaReceiverFetch
Handling send network completion with error: No Network Response Data
09-29 18:14:34.897 1796 2733 E [Link]: E[S
send]_MCDEpochCreateByData(284)=>Failed to find an existing network_requests row
( queue name = (null), sync database id = -1, network task identifier = 6BF45ED8-
A595-4A65-A8BA-9CCEA7243387): Error Domain=Facebook_MCD_epoch Code=200004
09-29 18:14:34.897 1796 2733 E [Link]: E[S
task_queue_processing]_handleServerSendNetworkErrorResponse(429)=>Task executor
failed to create epoch by network task identifier: Error Domain=Facebook_MCD_epoch
Code=200004
09-29 18:14:34.899 1796 2733 E [Link]: E[S
task_queue_handling]MCDLightSpeedTaskExecutorNetworkCompletionCallback(1131)=>Handl
ing send error for taskId=8199 batchSize=1 queue=acs_sync_LS_MediaReceiverFetch
Handling send network completion with error: No Network Response Data
09-29 18:14:34.900 1796 2733 E [Link]: E[S
send]_MCDEpochCreateByData(284)=>Failed to find an existing network_requests row
( queue name = (null), sync database id = -1, network task identifier = 9F080980-
59F4-460F-94B7-8AD6A2F3EA5A): Error Domain=Facebook_MCD_epoch Code=200004
09-29 18:14:34.901 1796 2733 E [Link]: E[S
task_queue_processing]_handleServerSendNetworkErrorResponse(429)=>Task executor
failed to create epoch by network task identifier: Error Domain=Facebook_MCD_epoch
Code=200004
09-29 18:15:38.061 917 982 E [Link]@2.0-service-mediatek:
akm_log setv_acc(720/g) -14, -48, 736 ts 71796593201
09-29 18:15:38.275 917 982 E [Link]@2.0-service-mediatek:
akm_log setv_mag(uT) 48.900002, 77.100006, -51.750004 ts 71796806365
09-29 18:15:59.435 917 982 E [Link]@2.0-service-mediatek:
akm_log setv_mag(uT) 48.150002, 81.150002, -51.750004 ts 71817966359
09-29 18:22:01.154 917 982 E [Link]@2.0-service-mediatek:
akm_log setv_mag(uT) 48.150002, 78.150002, -52.200001 ts 72179686356
09-29 18:22:40.010 917 982 E [Link]@2.0-service-mediatek:
akm_log setv_acc(720/g) -14, -48, 738 ts 72218541796
09-29 18:26:56.485 1796 1796 E [Link]: 0ms: IdentityHashReceiver
instantiating…
09-29 18:26:56.486 1796 1796 E [Link]: Main thread was blocked for
44ms in the background starting with IdentityHashReceiver
09-29 18:34:05.623 1796 1796 E [Link]: 0ms:
FbPushSdkFbnsReceiverShim instantiating…
09-29 18:34:05.624 1796 1796 E [Link]: Main thread was blocked for
34ms in the background starting with FbPushSdkFbnsReceiverShim
09-29 18:34:05.663 1796 7836 E [Link]: Flow is inactive
when adding debug checkpoint for instance key 200025944
09-29 18:34:05.710 1796 7836 I chatty : uid=10217([Link]) identical
1 line
09-29 18:34:05.718 1796 7836 E [Link]: Flow is inactive
when adding debug checkpoint for instance key 200025944
09-29 18:34:05.722 1796 7836 E [Link]: Flow is inactive
while trying to log push property annotations for instance key 200025944
09-29 18:34:05.724 1796 7836 E [Link]: Flow is inactive
while trying to log for message id: null, instance key: 200025944, mi trace id:
5627542628640595572
09-29 18:34:05.796 1796 7836 E [Link]: Flow is inactive
when adding debug checkpoint for instance key 200025944
09-29 18:35:16.649 917 982 E [Link]@2.0-service-mediatek:
akm_log setv_acc(720/g) -15, -48, 738 ts 72975179655
09-29 18:39:32.361 1796 1796 E [Link]: 0ms: FBPapayaJobService
instantiating…
09-29 18:39:32.362 1796 1796 E [Link]: Main thread was blocked for
21ms in the background starting with FBPapayaJobService
09-29 18:39:32.444 1796 13694 E [Link]: 1 onTaskStart
FOREGROUND modules:
[papaya(*),papayatorch,s_papayaanalyticstorch_papayatorch_torchedlooper(*),pytorch(
*),s_papayaanalyticstorch_papayatorch(*),s_papayatorch_torchedlooper(*)]
09-29 18:39:32.449 1796 13453 E [Link]: 1 onLoadBatchStart
FOREGROUND modules:
[papaya(*),papayatorch,s_papayaanalyticstorch_papayatorch_torchedlooper(*),pytorch(
*),s_papayaanalyticstorch_papayatorch(*),s_papayatorch_torchedlooper(*)]
09-29 18:39:32.451 1796 13694 E [Link]: 2 onTaskStart
FOREGROUND modules:
[papaya(*),s_papayaanalyticstorch_papayatorch_torchedlooper(*),papayaanalyticstorch
,pytorch(*),s_papayaanalyticstorch_papayatorch(*)]
09-29 18:39:32.458 1796 7842 E [Link]: 2 onLoadBatchStart
FOREGROUND modules:
[papaya(*),s_papayaanalyticstorch_papayatorch_torchedlooper(*),papayaanalyticstorch
,pytorch(*),s_papayaanalyticstorch_papayatorch(*)]
09-29 18:39:32.805 1796 7842 E [Link]: 2
onLoadBatchComplete exception: null FOREGROUND modules:
[papaya(*),s_papayaanalyticstorch_papayatorch_torchedlooper(*),papayaanalyticstorch
,pytorch(*),s_papayaanalyticstorch_papayatorch(*)]
09-29 18:39:32.814 1796 13453 E [Link]: 1
onLoadBatchComplete exception: null FOREGROUND modules:
[papaya(*),papayatorch,s_papayaanalyticstorch_papayatorch_torchedlooper(*),pytorch(
*),s_papayaanalyticstorch_papayatorch(*),s_papayatorch_torchedlooper(*)]
09-29 18:39:32.816 1796 7836 E [Link]: 2 onTaskComplete
[true,false,] FOREGROUND modules:
[papaya(*),s_papayaanalyticstorch_papayatorch_torchedlooper(*),papayaanalyticstorch
,pytorch(*),s_papayaanalyticstorch_papayatorch(*)]
09-29 18:39:32.819 1796 13453 E [Link]: 1 onTaskComplete
[true,false,] FOREGROUND modules:
[papaya(*),papayatorch,s_papayaanalyticstorch_papayatorch_torchedlooper(*),pytorch(
*),s_papayaanalyticstorch_papayatorch(*),s_papayatorch_torchedlooper(*)]
09-29 18:39:52.169 1796 1796 E [Link]: 0ms: SystemJobService
instantiating…
09-29 18:39:52.169 1796 1796 E [Link]: Main thread was blocked for
21ms in the background starting with SystemJobService
09-29 18:40:39.179 13889 14257 E native : E0000 00:00:1759146039.179672 14257
geller_cache.cc:286] Failed to process element for deletion: missing timestamp
09-29 18:41:27.876 1796 1796 E [Link]: 0ms:
FbPushSdkFbnsReceiverShim instantiating…
09-29 18:41:27.877 1796 1796 E [Link]: Main thread was blocked for
39ms in the background starting with FbPushSdkFbnsReceiverShim
09-29 18:41:27.946 1796 13715 E [Link]: Flow is inactive
when adding debug checkpoint for instance key 154011784
09-29 18:41:28.062 1796 13715 E [Link]: Flow is inactive
when adding debug checkpoint for instance key 154011784
09-29 18:41:28.077 1796 13715 E [Link]: Flow is inactive
when adding debug checkpoint for instance key 154011784
09-29 18:41:28.086 1796 13715 E [Link]: Flow is inactive
while trying to log push property annotations for instance key 154011784
09-29 18:41:28.093 1796 13715 E [Link]: Flow is inactive
while trying to log for message id: null, instance key: 154011784, mi trace id:
8166565813951046519
09-29 18:41:28.175 1796 13715 E [Link]: Flow is inactive
when adding debug checkpoint for instance key 154011784
09-29 18:51:23.265 917 982 E [Link]@2.0-service-mediatek:
akm_log setv_acc(720/g) -18, -46, 738 ts 73941796973
09-29 18:53:59.649 917 982 E [Link]@2.0-service-mediatek:
akm_log setv_mag(uT) 48.750004, 79.500000, -51.300003 ts 74098179611
09-29 18:54:52.030 1313 4192 D ConnectivityService: requestNetwork for
uid/pid:10217/1796 NetworkRequest [ TRACK_DEFAULT id=2016, [ Capabilities:
INTERNET&NOT_RESTRICTED&TRUSTED Uid: 10217 AdministratorUids: [] RequestorUid:
10217 RequestorPackageName: [Link]] ]

Common questions

Powered by AI

Several indicators in the logs suggest potential performance issues with the Facebook app. Notably, the ActivityManager shows high CPU usage, peaking at 112% with 96% user and 15% kernel times . Additionally, there are numerous minor and major faults, with a peak of 143,168 minor and 241 major , which indicate significant memory activity potentially caused by the application. The presence of SlowAppComponent messages also suggests blocked main thread operations, such as in the instantiation of services where the main thread was blocked for up to 297ms .

The sensor logs reveal the state of the device's accelerometer and magnetometer through repeated entries logged by android.hardware.sensors@2.0-service-mediatek . Values like '-14, -48, 738 ts' and magnetometer readings such as '48.900002, 77.100006, -51.750004 ts' denote ongoing sensor data collection possibly associated with tasks like navigation or fitness tracking . These consistent logs could imply active usage scenarios involving movement tracking or orientation sensing. The variance in values over timestamps could reflect physical activity or transport events experienced by the device.

The logs reflect several multithreading issues impacting application performance. For instance, thread blocking is evident with the Main thread blocked for durations, suggesting potential over-reliance on synchronous operations within Facebook services such as LollipopUploadService and ConditionalWorkerService . The stack traces showing calls to java.util.concurrent methods like FutureTask.run indicate attempts to manage tasks asynchronously, yet the existence of 'org.json.JSONException' and network task errors imply failures in handling concurrent operations efficiently . These lead to increased latency and degraded responsiveness in the app.

The logs show frequent sensor readings from the android.hardware.sensors@2.0-service-mediatek without error notifications, suggesting stability in how data is captured and processed . Consistently logged values, such as accelerometer outputs 'setv_acc(720/g) -18, -46, 738' and magnetometer logs, imply reliable data streams with no sign of sensor malfunction or interruption . The reliable and consistent logging indicates that the service maintains operational continuity even under sustained usage, though sensor performance and resultant battery consumption should be monitored.

Prominent network-related errors include data request errors indicating missing network responses, as shown by 'No Network Response Data' messages when handling various Facebook_MCD_epoch network task identifiers . These errors can severely impact functionality by obstructing data retrieval and synchronization processes, leading to incomplete operations such as the syncing and fetching of media or user data essential for app activities like feeds update or message transmission .

The network request logs indicate room for optimization in handling failed or incomplete data requests, reflected in entries like 'No Network Response Data' for task ID errors . These insights suggest analysis and enhancement opportunities in retry mechanisms and error diagnosis. Implementing more robust network reconnection logic and thorough logging to trace requests and responses could improve data flow reliability. Monitoring request lifetime and batching requests for efficiency may also reduce instances of task timeouts or data sync failures.

Thread blocking events reflected in log entries like 'Main thread was blocked for 297ms in the background starting with ConditionalWorkerService' indicate significant potential usability issues . Blocking on the main thread hinders UI responsiveness, leading to lag and unresponsive states. Such delays degrade the user experience by causing visible latencies in app interactions. To improve usability, refactoring tasks to offload heavy operations to background threads and ensuring non-blocking UI updates could alleviate these issues.

Flow logging, evident in lines with 'Flow is inactive when adding debug checkpoint', plays a crucial role in tracing application processes. It helps developers track execution paths and flow states, especially for complex interactions . However, messages about inactive flows suggest potential issues in lifecycle management or unhandled state transitions. These logs are vital for debugging by highlighting areas where state management improvements are needed or where flow activation should be controlled. Enhanced flow analysis can precisely identify bottleneck or faulty processes.

Evidence of high application resource usage includes CPU utilization reports where Facebook's com.facebook.katana process exhibits above-100% usage, suggesting it monopolizes resources at the expense of other applications . Fault logs reflect heavy memory activity with extensive minor and major faults. Mitigation strategies could include optimizing the app’s memory management to reduce paging, implementing lazy loading techniques to defer resource-intensive tasks, and refactoring for asynchronous execution to lower CPU burden.

The exceptions such as 'org.json.JSONException: No value for new_locale' highlighted in the logs hint at handling failures during JSON parsing, potentially due to missing or unexpected input data during API responses or integration points . Also, 'ThreadPoolExecutor' errors might stem from improper task scheduling or resource exhaustion, causing execution failures. Causes could include inadequate error handling for fallback procedures in asynchronous data parsing or improper management of available workers in multi-thread processing within concurrent operations.

You might also like