Bug 233006

Summary: Regression: Missing textures on ios15
Product: WebKit Reporter: akul
Component: WebGLAssignee: Nobody <webkit-unassigned>
Status: NEW    
Severity: Normal CC: dino, florent.masson, kbr, kkinnunen, webkit-bug-importer
Priority: P2 Keywords: InRadar
Version: Safari 15   
Hardware: Unspecified   
OS: Unspecified   
Bug Depends on: 231471    
Bug Blocks:    
Attachments:
Description Flags
ios15, missing texture (middle of the field is black)
none
ios14, working as expected, texture in the middle of the field is present none

akul
Reported 2021-11-11 11:32:11 PST
Created attachment 443983 [details] ios15, missing texture (middle of the field is black) Referencing the original issue from here: https://discourse.threejs.org/t/textures-in-gltf-sometimes-display-black-but-only-on-ios/30520/2 Repo app: https://hc1vv.csb.app/ Code: https://codesandbox.io/s/three-js-gltf-stadium-hc1vv?file=/index.js iOS14: Works as expected, all three textures are loaded iOS15.0.2 / iOS15.2: [regression] Behavior 1) Missing textures (ie one or more of the textures is black). Behavior 2) Page reloads or crashes (potential memory issue) Behavior 3) It should also be noted that it takes a significantly longer time to load the textures on iOS15 vs iOS14 Tested with these combinations with the same effect: [GPU Process: WebGL, GPU Process: Canvas Rendering, WebGL via Metal, WebGL 2.0] Another example of this issue: https://discourse.threejs.org/t/missing-textures-on-safari-ios15/30245
Attachments
ios15, missing texture (middle of the field is black) (232.57 KB, image/png)
2021-11-11 11:32 PST, akul
no flags
ios14, working as expected, texture in the middle of the field is present (1.48 MB, image/png)
2021-11-11 11:35 PST, akul
no flags
akul
Comment 1 2021-11-11 11:35:14 PST
Created attachment 443984 [details] ios14, working as expected, texture in the middle of the field is present
Kenneth Russell
Comment 2 2021-11-11 17:57:46 PST
Likely duplicate of Bug 231471.
Radar WebKit Bug Importer
Comment 3 2021-11-18 11:33:23 PST
Note You need to log in before you can comment on or make changes to this bug.