Open tqtifnypmb opened 3 months ago
This is throwing an exception in the evaluation thread -- this should have printed a message in the crash log. Did you see anything like that?
This is throwing an exception in the evaluation thread -- this should have printed a message in the crash log. Did you see anything like that?
This issue never occurred to me during development, so I did not see any printed message, for now I only have crash logs from iOS devices.
Near the top of the crash log it may have some more specific information. Something along these lines:
Crashed Thread: 1 Dispatch queue: setup-queue
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Termination Reason: Namespace SIGNAL, Code 6 Abort trap: 6
Terminating Process: fileproviderd [12223]
Application Specific Information:
Assertion failed: (Unexpected function requested: existing (null), requested (null)), function xxx
I found no Application Specific Information
section among the logs I have.
However, I noticed that all the devices that crashed are quite old models (iPhone 10, iPhone 11, iPad 8, iPad 11). I'm not sure if the issue is related to their chips.
AppVariant: 1:iPad11,3:16
Code Type: ARM-64 (Native)
Role: Foreground
Parent Process: launchd [1]
Date/Time: 2024-07-27 10:43:59.2120 +0200
Launch Time: 2024-07-27 10:43:45.7787 +0200
OS Version: iPhone OS 17.5.1 (21F90)
Release Type: User
Report Version: 104
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Termination Reason: SIGNAL 6 Abort trap: 6
Triggered by Thread: 12
Thread 12 crashed with ARM Thread State (64-bit):
x0: 0x0000000000000000 x1: 0x0000000000000000 x2: 0x0000000000000000 x3: 0x0000000000000000
x4: 0x00000001fb8feea6 x5: 0x000000000000000e x6: 0x0000000000000020 x7: 0x0000000000000450
x8: 0xa0a9d41e6bff9b04 x9: 0xa0a9d41f1bc16b04 x10: 0x0000000000001b00 x11: 0x00000001703edd60
x12: 0x00000000000007fb x13: 0x00000000000007fd x14: 0x0000000000000010 x15: 0x0000000000000037
x16: 0x0000000000000148 x17: 0x00000001703ef000 x18: 0x0000000000000000 x19: 0x0000000000000006
x20: 0x000000000000c407 x21: 0x00000001703ef0e0 x22: 0x0000000205e678a0 x23: 0x000000010617e740
x24: 0x0000000301c7b780 x25: 0x00000001703eea68 x26: 0x00000001703eec40 x27: 0x0000000300b0ed60
x28: 0x7ffffffffffffff8 fp: 0x00000001703ee1a0 lr: 0x00000001f6df1c0c
sp: 0x00000001703ee180 pc: 0x00000001e309342c cpsr: 0x40000000
esr: 0x56000080 Address size fault
Yes, that likely is an issue -- older GPUs didn't support the same Metal capabilities. I know mlx-swift works on an iPhone 12 Pro Max but I haven't tested on anything older.
There are some more details here: https://github.com/ml-explore/mlx-swift-examples/issues/21
Describe the issue:
There is a chance that mlx would causes
Address size fault
crashes whileeval
the graph on iOS devices. This issue barely occur on macOS devices.Configuration:
Devices: iPhone/iPad System Version: From iOS 16.7 to iOS 17.5 MLX-Swift version: 0.16.0
Crash Logs:
How to reproduce?
Don't know. This issue seems to occur occasionally. Can't provide meaningful code neither.