Bug 235719

Summary: STP 139 Pages no longer load on first try
Product: WebKit Reporter: Jack Wellborn <w0nka>
Component: Page LoadingAssignee: Nobody <webkit-unassigned>
Status: RESOLVED DUPLICATE    
Severity: Major CC: beidson, bfulgham, cdumez, pvollan
Priority: P2    
Version: Safari Technology Preview   
Hardware: Mac (Apple Silicon)   
OS: macOS 12   
Attachments:
Description Flags
Video of Page Loading Issue none

Jack Wellborn
Reported 2022-01-27 09:04:01 PST
Created attachment 450144 [details] Video of Page Loading Issue Hello, Upon updating Safari Technology Preview to version 139 and macOS to version 12.2, I found that some pages no longer load on first try. This doesn't seem to be a network issue as they load immediate upon retrying. I have tried restarting Safari Technology Preview to no avail. Included is a video of behavior. Environment Apple Silicon MacBook Pro macOS 12.2 Safari Technology Preview 139 Reproduction Steps: 1. Open Safari Technology Preview 2. Navigate to different valid pages using the url bar. Expected behavior: All valid pages load. Actual behavior: Some pages don't load until retry. Thanks, Jack
Attachments
Video of Page Loading Issue (28.68 MB, video/quicktime)
2022-01-27 09:04 PST, Jack Wellborn 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
Chris Dumez
Comment 1 2022-01-27 09:09:41 PST
Per, I think this is the sandboxing issue you've been working on.
Chris Dumez
Comment 2 2022-01-27 09:10:17 PST
If so, this is likely a dupe of Bug 235186.
Chris Dumez
Comment 3 2022-01-27 09:49:41 PST
It looks like STP 139 didn't ship with the fix for Bug 235186 and is thus seeing the random load hangs we were seeing before that fix.
Per Arne Vollan
Comment 4 2022-01-27 13:02:05 PST
*** This bug has been marked as a duplicate of bug 235186 ***
Per Arne Vollan
Comment 5 2022-01-27 13:02:41 PST
(In reply to Chris Dumez from comment #2) > If so, this is likely a dupe of Bug 235186. Yes, I believe that is a dupe of Bug 235186.
Note You need to log in before you can comment on or make changes to this bug.