-
Notifications
You must be signed in to change notification settings - Fork 760
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
EXCEPTION_ACCESS_VIOLATION #858
Comments
SQLDump00001.txt:
SQLDump00002.txt:
|
And updating Docker to 4.24.0 seems to have fixed this. I'm not sure if I should just close the issue, or you would like to investigate it anyway. |
I have the exact same issue. It started when i updated to Mac OS Sonoma. Worked fine before. Logs looks very similar. I'm on Docker 4.24.0, but still get this now and then. I have also tried various different SQL Docker images. |
Well, yeah. It's back for me again. I have no idea why did it work once right after the Docker update. |
For me it works "for a bit" and then boom, kind of randomly it seems like. |
Currently the workaround I have found is to start the container with environment variable MSSQL_PID="Standard" (Developer and Enterprise editions seems to enable / use assembly instructions not invoked in Standard edition). Please note that this workaround comes with compromises :(
Hope this helps people out whilst either apple or docker sorts out the x64 emulation regression. |
I've tried to set "Standard" but it seems not to help for me. Still crashing pretty often, but kind of randomly it seems.
|
Unfortunately my only suggestion is to revert back to Ventura from Sonoma. That will make everything work as before. |
I can vouch for the reverting back to Ventura... I used this video if it may help: https://www.youtube.com/watch?v=QiOQqaa0t0E |
I've also downgraded to Ventura, lesson learned. Always wait a few patches before upgrading your OS 🤷♂️ |
Linking this: docker/roadmap#384 |
This was fixed for me by upgrading to Sonoma 14.1 (beta, 23B73). See this thread: docker/for-mac#7006. |
I get something similar on Linux starting today, when I upgrading to linux 6.7 kernel. Tried it on another machine to validate that it is indeed the update.
|
Same |
I am getting this issue on Sonoma 14.5. Happened after I updated my OS. |
I am seeing this issue on Sonoma 14.5. Upgraded Docker to v4.30, no changes. |
This appears to be related docker/for-mac#7006 I'm on Sonoma 14.5 (M3 chip), Docker Desktop v4.30 with Rosetta emulation enabled for x86/amd64 translation. The SQL Server 2019 (latest) amd64 container would crash under load quite often.
After downgrading to Docker Desktop for Mac v4.27.2 the issues are gone. It's unclear to me if this is an issue with Docker Desktop for Mac, Rosetta emulation, or possibly both. But downgrading Docker Desktop appears to have resolved the issue for now. |
I was experiencing issues restoring a known good .bacpac file that repeatedly hung during the import. Rolling back from Mac Docker Desktop 4.31.0 to 4.27.2 resolved this. Environment: |
I am also facing this issue with Environment: It is resolved by upgrading to Desktop 4.32.0 |
After upgrading to Sonoma 14.6, and Docker Desktop 4.33.0 I am yet facing this issue again. See:
|
I am on M3 Pro Sonoma and Docker Desktop 4.33.0 (160616) but still same issue
|
mcr.microsoft.com/mssql/server:2022-latest
. (This worked for me ~a month ago, and I know that there was an update of the image in September, but going back to the August version didn't seem to make a difference.)EXCEPTION_ACCESS_VIOLATION
.The text was updated successfully, but these errors were encountered: