User Profile
Eric_Lawrence
Joined 7 years ago
User Widgets
Recent Discussions
Re: Edge: DNS Flush
Many things seem like they should be "simple" but are quite complicated if you look at the full set of components involved. Which DNS resolver are you configured to use? Beyond the DNS cache in the browser, the OS maintains its own cache of DNS resolutions. Did you clear that? Do you have a NETLOG showing a cached DNS record being used? Did you already have active connections to the hostname in question in the browser's keep-alive pool?3.3KViews0likes0CommentsRe: [FIXED] Problem: Can't open unsafe ports on Edge insider
wasilis92 The only thing you really should need to disable is Startup Boost -- that's the one that keeps a background Edge process around. Efficiency Mode and Sleeping tabs do NOT keep extra processes. See https://textslashplain.com/2022/01/05/edge-command-line-arguments/#:~:text=An%20argument%20I%20tried%20didn%E2%80%99t%20seem%20to%20do%20anything%3F%20Why%20not%3F for discussion. As for why Edge uses many processes-- Chromium-based browsers use many processes for security and reliability reasons. Each process can have its own sandbox, with restrictions locked down as tight as possible for that process' job. Similarly, if a utility process crashes, the browser does not crash and the utility can be restarted.3.2KViews1like1CommentRe: Edge: DNS Flush
There's nothing wrong with sending that set of Cache-Control headers; they'll be treated as |no-store|. Having said that, Cache-Control headers don't apply to every layer of caching in the browser, so they're not a complete guarantee against reuse of a response. But on a full-page navigation, they should be effective. The thing you want to look at in the netlog is the DNS transaction entries.209KViews0likes0CommentsRe: Edge: DNS Flush
Menoblack That should not be the case, no. If anything, it should be the opposite (if you have a web page entirely in the cache, or if you have a serviceworker installed by the target site, your browser might not need to connect to the server at all). If you have a NetLog (https://textslashplain.com/2020/01/17/capture-network-logs-from-edge-and-chrome/) from your failing scenario, you could look to see what precisely is happening with DNS resolutions.212KViews0likes2CommentsRe: Edge Beta crashing as of Jan 20, 2023 after update i guess
In virtually all cases, code fixes go to all platforms at the same time, so whenever you get the latest version (edge://version), you'll have the same code as on other platforms. Similarly, ECS flag updates all go out at the same time, but because of how the client checks these, it may be several hours before you see the change between different computers. Have you verified that the command line argument workaround works? If it doesn't, can you share an Uploaded Crash Report ID?2.9KViews0likes0CommentsRe: Edge Beta crashing as of Jan 20, 2023 after update i guess
Disabling the features temporarily is harmless and you're unlikely to notice any difference. In /theory/, the buggy code has already been disabled by experimental config flags from the server (see https://textslashplain.com/2019/07/16/updating-browsers-quickly-flags-respins-and-components/#:~:text=using%20OmahaProxy.-,Field%20Trial%20Flags,-In%20some%20cases) which means you shouldn't need the command line arguments any longer.5.7KViews2likes7CommentsRe: Edge Beta crashing as of Jan 20, 2023 after update i guess
To pass arguments on Mac, use Terminal to launch. 1. Verify all instances are closed in Activity Monitor (or whatever Mac task manager) 2. Run /Applications/Microsoft\ Edge\ Beta/Contents/MacOS/Microsoft\ Edge\ Beta --disable-features=msTriggeringSignalGenerator,msTriggeringUseAssetDeliveryService https://textslashplain.com/2022/01/05/edge-command-line-arguments/#:~:text=command%20line%20arguments%20on%20Mac%20OS5.8KViews1like1CommentRe: Edge Beta crashing as of Jan 20, 2023 after update i guess
Thanks. I've confirmed that your crash ID matches the known issue that we're tracking and fixing. The workaround has been effective for other folks that have tried it. The one known reason why it wouldn't work is if you already had an Edge instance in the background (because Edge only respects arguments passed to the very first instance). You can verify whether your current browser "sees" the argument by looking for it on the edge://version page as described in https://textslashplain.com/2022/01/05/edge-command-line-arguments/#:~:text=An%20argument%20I%20tried%20didn%E2%80%99t%20seem%20to%20do%20anything%3F%20Why%20not%3F6.1KViews0likes0CommentsRe: Edge Beta crashing as of Jan 20, 2023 after update i guess
Dave_Gleason_DGNorCal Sorry for the inconvenience. The fix should be released shortly. Until then a workaround may be: Close all instances (verify in task manager) msedge.exe --disable-features=msTriggeringSignalGenerator,msTriggeringUseAssetDeliveryService If that doesn’t help, please retreat to the stable channel.7.5KViews5likes26CommentsRe: Edge Stable 103.0.1264.37 breaks group policy management of the browser - Critical
It appears that the rollout has started: https://twitter.com/ericlaw/status/1542593747766083585. I'm afraid I do not myself know the specifics about the rate at which rollout occurs, but the team does understand the importance of getting broad deployment quickly.4KViews1like9CommentsRe: Edge Stable 103.0.1264.37 breaks group policy management of the browser - Critical
This issue is caused by a race condition. Group Policy update works by 1) Deleting the old policies from the registry 2) Writing the current policies to the registry 3) Chromium reloading new policy data out of the registry In v103, a regression was introduced by new registry-monitoring code. This code would detect that the keys had changed at [point 1] and the browser's in-process policy would be refreshed before the current policy data had been fully written to the registry by the GP Update. As a consequence, the browser process could end up with a "partial" (or empty) set of policies applied. The problem's reproducibility will vary depending upon how short the time gap is between old policies being deleted from the registry and new policies being written. The visibility of the problem also varies-- only policies that support Dynamic Refresh are impacted, and many policies do not have side-effects that are immediately user-visible. The fix is to stop monitoring the registry keys directly.12KViews0likes19Comments
Recent Blog Articles
No content to show