New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 908525 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Nov 28
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

no-bypass-main-world-csp-for-delayed-execution.html webkit_layout_tests failing on chromium.webkit/WebKit Linux Trusty MSAN

Project Member Reported by chcunningham@chromium.org, Nov 26

Issue description

3 test failures

* http/tests/security/isolatedWorld/no-bypass-main-world-csp-for-delayed-execution.html
* virtual/outofblink-cors-ns/http/tests/security/isolatedWorld/no-bypass-main-world-csp-for-delayed-execution.html
* virtual/outofblink-cors/http/tests/security/isolatedWorld/no-bypass-main-world-csp-for-delayed-execution.html
 

Across several failed builds

https://ci.chromium.org/buildbot/chromium.webkit/WebKit%20Linux%20Trusty%20MSAN/11193
https://ci.chromium.org/buildbot/chromium.webkit/WebKit%20Linux%20Trusty%20MSAN/11192
https://ci.chromium.org/buildbot/chromium.webkit/WebKit%20Linux%20Trusty%20MSAN/11191
https://ci.chromium.org/buildbot/chromium.webkit/WebKit%20Linux%20Trusty%20MSAN/11190



 
Cc: mkwst@chromium.org
Owner: creis@chromium.org
Seems like these tests came a while back. jww no longer here, so assigning some security folks. 
Cc: lukasza@chromium.org creis@chromium.org dcheng@chromium.org
Components: Blink>SecurityFeature
Owner: yukishiino@chromium.org
I'm not familiar with CSP code.  From the logs, it looks like this is failing the following check in ShouldAllowAccessToV8ContextInternal, which yukishiino@ touched in r609198:
 CHECK_EQ(accessing_world.GetWorldId(), target_world.GetWorldId());

Maybe you can take a look or help route to the right person?  (CC'ing lukasza@ in the off chance this is related to Site Isolation being enabled for layout tests.)
Status: Fixed (was: Untriaged)
I think that https://chromium-review.googlesource.com/c/chromium/src/+/1351424 fixed this issue.

Sign in to add a comment