Bug 235719 - STP 139 Pages no longer load on first try
Summary: STP 139 Pages no longer load on first try
Status: RESOLVED DUPLICATE of bug 235186
Alias: None
Product: WebKit
Classification: Unclassified
Component: Page Loading (show other bugs)
Version: Safari Technology Preview
Hardware: Mac (Apple Silicon) macOS 12
: P2 Major
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-01-27 09:04 PST by Jack Wellborn
Modified: 2022-01-27 13:02 PST (History)
4 users (show)

See Also:

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 an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Jack Wellborn 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
Comment 1 Chris Dumez 2022-01-27 09:09:41 PST 
Per, I think this is the sandboxing issue you've been working on.
Comment 2 Chris Dumez 2022-01-27 09:10:17 PST 
If so, this is likely a dupe of Bug 235186.
Comment 3 Chris Dumez 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.
Comment 4 Per Arne Vollan 2022-01-27 13:02:05 PST 

*** This bug has been marked as a duplicate of bug 235186 ***
Comment 5 Per Arne Vollan 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.