-
Notifications
You must be signed in to change notification settings - Fork 26.8k
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
[Impeller] Play/RendererTest.DefaultIndexSize/Vulkan: X Error of failed request: BadAccess (attempt to access private resource denied) #116130
Comments
@akbiggs FYI |
I don't think that failure is even making it to the test itself, might be a different issue. FYI @iskakaushik |
So, IIUC, you are saying that the failure is unrelated to the stack trace shown? |
The failure seems unrelated to the contents of the test itself. its failing in the setup code and not in the test body |
We may be accessing a thread local on a thread that is terminating in the unit-test harness. If I had to guess, the Vulkan backend in Impeller does create a separate thread to wait on fences and such. Perhaps that's the thread? cc @iskakaushik |
I can reproduce this by running The X client library is sometimes getting an error, and after logging the "failed request" message it calls That causes destruction of global objects, including the But other threads may still be running while The Impeller Vulkan tests are using Xvfb. I don't know why the interaction with Xvfb is sometimes producing these X protocol errors. |
Stack trace of the Xlib API failure:
|
@jason-simmons could this be because xvfb setup isn't complete yet? see: https://github.com/flutter/engine/blob/40019b79d4f84bbadc7412b76b6a4daf88295c8c/testing/xvfb.py#L100, maybe we should increase the timeout here? |
This is happening midway through the Impeller/Vulkan test suite. Xvfb is running and many tests have successfully completed by the time this error happens. |
The "Major opcode of failed request: 130" message corresponds to the MIT-SHM X extension. So I tried disabling that by adding That appears to work around this issue. I've been running the Impeller/Vulkan tests repeatedly on my Linux setup with that patch and have not seen this error. |
…Impeller/Vulkan unit tests See flutter/flutter#116130
…Impeller/Vulkan unit tests (#38092) See flutter/flutter#116130
I don't think has been recurring. can we close this issue? |
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of |
This error breaks the ICU roller into Fuchsia. The error seems unrelated to the roller - the ICU library has nothing to do with graphics output.
Steps to Reproduce
See: https://logs.chromium.org/logs/flutter/buildbucket/cr-buildbucket/8796611293756295121/+/u/test:_Host_Tests_for_host_debug_impeller_vulkan__3_/stdout
Logs
The text was updated successfully, but these errors were encountered: