It looks like we were relying on undefined behavior in initializing the memory threshold, and the that the Apple silicon builder uses a different initialization order. We should avoid checking the ProcessInfo until runtime.
Fix BucketCatalog memory threshold initialization
- Assignee:
-
Dan Larkin-York
- Reporter:
-
Dan Larkin-York
- Votes:
-
0 Vote for this issue - Watchers:
-
3 Start watching this issue
- Created:
- Updated:
- Resolved: