FLEX crashes when inspecting a specific object in WhatsApp.
Ram4096 opened this issue · comments
Environment
- Platform: iOS 13.5.
- FLEX Version: 4.4.0.
Bug Report
If I try to inspect an object of type "WAUserSessionPreferences" from Heap Objects, the app crashes. Unfortunately I have not a crash log, but this happens since a long time. Can you please inspect that object, in order to read the crash log and to apply a fix, if possible? Thanks!
Do you have Cr4shed or Crash Reporter installed?
Hi, sorry for the delay! This is the crash log:
Date: 4/24/21, 1:27 AM
Process: WhatsApp
Bundle id: net.whatsapp.WhatsApp
Device: iPhone 8, iOS 14.3
Bundle version: 2.21.72
Exception type: EXC_BAD_ACCESS (SIGSEGV)
Exception subtype: KERN_INVALID_ADDRESS: 0x0
Exception codes: 0x0000000000000001, 0x0000000000000000
Culprit: libFLEX.dylib
VM Protection: 0x0 is not in any region.
Triggered by thread: 0
Thread name: Dispatch queue: com.apple.main-thread
Call stack:
0 libFLEX.dylib 0x0000000108154770 0x10807c000 + 886640 // +[FLEXRuntimeUtility performSelector:onObject:withArguments:error:]
1 libFLEX.dylib 0x0000000108154770 0x10807c000 + 886640 // +[FLEXRuntimeUtility performSelector:onObject:withArguments:error:]
2 libFLEX.dylib 0x00000001081543e4 0x10807c000 + 885732 // +[FLEXRuntimeUtility performSelector:onObject:]
3 libFLEX.dylib 0x0000000108163284 0x10807c000 + 946820 // -[FLEXProperty getValue:]
4 libFLEX.dylib 0x000000010816333c 0x10807c000 + 947004 // -[FLEXProperty getPotentiallyUnboxedValue:]
5 libFLEX.dylib 0x0000000108177a44 0x10807c000 + 1030724 // -[FLEXProperty(UIKitHelpers) currentValueWithTarget:]
6 libFLEX.dylib 0x0000000108177c44 0x10807c000 + 1031236 // -[FLEXProperty(UIKitHelpers) previewWithTarget:]
7 libFLEX.dylib 0x00000001080a4458 0x10807c000 + 164952 // -[FLEXMetadataSection subtitleForRow:]
8 libFLEX.dylib 0x00000001080a5668 0x10807c000 + 169576 // -[FLEXMetadataSection configureCell:forRow:]
9 libFLEX.dylib 0x000000010808c6a0 0x10807c000 + 67232 // -[FLEXFilteringTableViewController tableView:cellForRowAtIndexPath:]
10 UIKitCore 0x00000001a97bb6f8 0x1a8a79000 + 13903608 // -[UITableView _createPreparedCellForGlobalRow:withIndexPath:willDisplay:]
11 UIKitCore 0x00000001a9789178 0x1a8a79000 + 13697400 // -[UITableView _updateVisibleCellsNow:]
12 UIKitCore 0x00000001a97a65cc 0x1a8a79000 + 13817292 // -[UITableView layoutSubviews]
13 UIKitCore 0x00000001a9ab1448 0x1a8a79000 + 17007688 // -[UIView(CALayerDelegate) layoutSublayersOfLayer:]
14 QuartzCore 0x00000001a9fb6f2c 0x1a9e61000 + 1400620 // -[CALayer layoutSublayers]
15 QuartzCore 0x00000001a9fbd4d0 0x1a9e61000 + 1426640 // CA::Layer::layout_if_needed(CA::Transaction*)
16 QuartzCore 0x00000001a9fc8820 0x1a9e61000 + 1472544 // CA::Layer::layout_and_display_if_needed(CA::Transaction*)
17 QuartzCore 0x00000001a9f14160 0x1a9e61000 + 733536 // CA::Context::commit_transaction(CA::Transaction*, double, double*)
18 QuartzCore 0x00000001a9f3e324 0x1a9e61000 + 906020 // CA::Transaction::commit()
19 UIKitCore 0x00000001a95d75a8 0x1a8a79000 + 11920808 // _afterCACommitHandler
20 CoreFoundation 0x00000001a6cbd87c 0x1a6c24000 + 628860 // CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION
21 CoreFoundation 0x00000001a6cb7f50 0x1a6c24000 + 606032 // __CFRunLoopDoObservers
22 CoreFoundation 0x00000001a6cb8498 0x1a6c24000 + 607384 // __CFRunLoopRun
23 CoreFoundation 0x00000001a6cb7ba0 0x1a6c24000 + 605088 // CFRunLoopRunSpecific
24 GraphicsServices 0x00000001bd9f5598 0x1bd9f2000 + 13720 // GSEventRunModal
25 UIKitCore 0x00000001a95a73d8 0x1a8a79000 + 11723736 // -[UIApplication _run]
26 UIKitCore 0x00000001a95ac958 0x1a8a79000 + 11745624 // UIApplicationMain
27 WhatsApp 0x0000000104e99c88 0x104a1c000 + 4709512
28 libdyld.dylib 0x00000001a6996568 0x1a6995000 + 5480 // start
I think I forgot to reply to this, my apologies.
I don't really have the time to investigate these oddities in specific apps anymore. If you can debug it yourself I can help from there. Do you know how to debug third party apps with Xcode?
I'm closing this for now, but you're welcome to convert it to a Discussion topic instead, if you want it to continue to get visibility.