13:22:14 nick /dr00tb 17:36:39 hi folks - I'm seeing a segmentation fault around 99% complete sync on ARM64 macOS/Darwin 17:37:06 I've tried on multiple occasions, nothing obvious in logs. On 0.18.2.2 17:37:17 anything reported/known, before I make a GH issue? 17:38:05 verbose logging simply shows: ```2023-05-04 09:25:36.240 T Blockchain::have_block_unlocked 17:38:05 2023-05-04 09:25:36.240 T BlockchainLMDB::block_exists 17:38:05 2023-05-04 09:25:36.240 T BlockchainLMDB::block_rtxn_start 17:38:06 2023-05-04 09:25:36.240 T Block with hash c28336da72d1abc42b5c4adb785d8dc0debc779a614a86ef8d43305000b5eea0 not found in db 17:38:06 2023-05-04 09:25:36.240 T mdb_txn_safe: destructor 17:38:06 2023-05-04 09:25:36.240 T BlockchainLMDB:: get_alt_block 17:38:06 2023-05-04 09:25:36.240 T BlockchainLMDB::block_rtxn_start 17:38:07 2023-05-04 09:25:36.240 T mdb_txn_safe: destructor``` 17:39:58 when I say I've tried on 'multiple occasions' I mean, I've resyncd 3 times. 17:54:24 Get a stack trace with gdb. 17:54:46 ie, gdb /path/to/monerod path/to/core ; bt 17:55:00 Or coredumpctl debug if you have systemd 17:55:58 john_alan_: self compiled? 17:56:06 or how did you install it? 17:57:09 I assume this issue will be relevant https://github.com/monero-project/monero/issues/8657 17:57:18 hey both 17:57:23 installed via home-brew 17:57:38 (on macOS), happy to help debug, checking out 8657 now... 17:57:45 you have to use the release binaries from getmonero.org 17:58:16 or you have to set `MONERO_RANDOMX_UMASK=8` env var, both work 17:59:04 ahhhh 17:59:10 so home-brew default is broken? 17:59:44 it's not homebrew's fault and it's unclear if this is a macos bug or not 18:00:18 this is a bottled version I'm using form homebrew i.e. not compiled locally, we could add a fix to their build script 18:00:28 moneromooo: does this look like a serialization issue on 32bit? https://github.com/monero-project/monero/issues/8837#issuecomment-1536588024 18:01:17 happy to file with homebrew if not already done, either way, thanks both. 18:02:10 john_alan_: I'm didn't file any issue yet for it, I feel like they will say we should fix it on our side 18:03:35 ya I get you, arm64 bin from getmonero is working 18:03:37 how weird 18:03:42 I wonder what the root cause is 18:05:11 I guess some weird JIT security thing 18:05:19 RandomX cache invalidation somehow isn't working 18:05:20 I remember macOS treats JIT differently to BSD 18:05:34 but this whole thing only started happening on macOS 13 so we assumed it's a macOS bug 18:05:35 macOS security issue? 18:06:01 related to JITc tho right? 18:06:15 I don't think it's a security issue, just JIT cache invalidation isn't working causing it to calculate wrong hashes 18:06:27 MONERO_RANDOMX_UMASK=8 disables JIT 18:06:44 thanks selsta, does that impact performance? 18:06:58 yes 18:07:12 when I mean security, I mean macOS is being weird on security causing JIT to behave funny 18:07:17 they keep messing with JIT rules 18:08:44 there's this document and we do everything that's written there https://developer.apple.com/documentation/apple-silicon/porting-just-in-time-compilers-to-apple-silicon 18:19:32 Thanks selsta 20:54:02 selsta: probably 20:54:47 Something reading unaligned words (I assume their arch doesn't like that, which is usually what bus errors means). 21:15:57 @selsta: does disable randomX JIT have any other impact outside of performance?