-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Xcode 14.3 (clang 14.0.3) crash on alloc_slab.cpp #8233
Comments
Hi @dabaicaifen I was able to reproduce your issue on my local and it seems like your finding are correct. I'm generating a report with the issues which may be causing this to happen, and try to solve them. |
I've occasionally run the clang static analyzer on our code and it's generally just been a mix of false positives and irrelevant things, so we've never set it as a goal to get zero warnings from it. It looks like there's currently a few very minor correct things and a bunch of incorrect things. |
Any update? |
@dabaicaifen There are a couple of PR (#8249 and realm/realm-core#6675) which solve some of the warnings |
While there are a handful of static analyzer warnings, they are very unlikely to be related to a crash in alloc_slab and we will need details about the actual problem you are hitting to be able to do anything. |
I can easily reproduce the crash with a fresh new project, have you tried it? @tgoyne |
@dabaicaifen Could you send us a sample app that reproduces this issue? |
We do indeed have tests and they don't crash. |
@tgoyne please use this demo https://github.com/dabaicaifen/RealmDemo/tree/analyze-crash, the branch is analyze-crash. And use Xcode 14.3 or 14.3.1. |
I can confirm that this issue exists and continues to be a thorn when using Realm. The warnings are not the problem, but rather a segmentation fault on Here's a stack trace of the issue on my local machine:
|
Are there any solutions I can apply now? |
How frequently does the bug occur?
Always
Description
I recently upgraded to Xcode 14.3 and our application always failed at Xcode analyze task.
I can reproduce the issue with a fresh new project, just add Realm references, and run Analyze from Xcode.
Stacktrace & log output
No response
Can you reproduce the bug?
Always
Reproduction Steps
Run Analyze from Xcode.
Version
10.38.3
What Atlas Services are you using?
Local Database only
Are you using encryption?
Yes
Platform OS and version(s)
16.4
Build environment
Xcode version: 14.3
Dependency manager and version: 10.38.3
The text was updated successfully, but these errors were encountered: