Home

Chromium issue on Windows

%3CLINGO-SUB%20id%3D%22lingo-sub-430599%22%20slang%3D%22en-US%22%3EChromium%20issue%20on%20Windows%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-430599%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%20I'm%20really%20loving%20the%20new%20Edge%20(already%20some%20noticeable%20improvements%20over%20Chrome!)%20but%20I%20hope%20the%20Edge%20team%20will%20take%20a%20look%20at%20a%20couple%20of%20issues%2C%20specifically%20this%20one%20(I%20know%20it's%20marked%20as%20Fixed%20but%20I%20know%20many%20that%20would%20differ)%20%3CA%20href%3D%22https%3A%2F%2Fbugs.chromium.org%2Fp%2Fchromium%2Fissues%2Fdetail%3Fid%3D522201%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fbugs.chromium.org%2Fp%2Fchromium%2Fissues%2Fdetail%3Fid%3D522201%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAlso%2C%20there%20are%20a%20number%20of%20v-sync%20issues%20with%20Chromium%20on%20Windows%2C%20some%20of%20them%20are%20listed%20here%20%3CA%20href%3D%22https%3A%2F%2Fwww.vsynctester.com%2Fchromeisbroken.html%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fwww.vsynctester.com%2Fchromeisbroken.html%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-430950%22%20slang%3D%22en-US%22%3ERE%3A%20Chromium%20issue%20on%20Windows%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-430950%22%20slang%3D%22en-US%22%3EEdge%20collects%20crash%20data%20using%20the%20crash%20reporting%20system.%20Can%20you%20please%20be%20precise%20about%20the%20set%20of%20repro%20steps%20you're%20using%20that%20cause%20Edge%20to%20crash%2C%20and%20what%20version%20of%20Edge%20and%20Windows%20you%20are%20running%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-431432%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20Chromium%20issue%20on%20Windows%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-431432%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F317619%22%20target%3D%22_blank%22%3E%40ericlaw%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESorry%20I%20should%20made%20been%20more%20clear.%20They%20did%20kinda%20fix%20that%20issues%20years%20ago%20but%20if%20you%20take%20the%20time%20to%20read%20through%20that%20issue%20report%2C%20I%20think%20you'll%20agree%20that%20some%20changes%20need%20to%20be%20made%20there%20(I'll%20just%20paste%20one%20of%20the%20comments%20from%20it%3A%20%22%3CSPAN%20class%3D%22line%22%3EYou%20are%20relying%20on%20the%20System%20Service%20Call%20Stub%20ASM%20layout%20on%20the%2064bit%20kernel.%20That%20is%20beyond%20wrong.%20Why%20are%20you%20relying%20on%20that%3F%20It%20is%20incredibly%20fragile%20and%20hinders%20Microsoft's%20ability%20to%20innovate.%3C%2FSPAN%3E%22%20)%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-431576%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20Chromium%20issue%20on%20Windows%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-431576%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F317619%22%20target%3D%22_blank%22%3E%40ericlaw%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3Emore%3C%2FP%3E%3CP%3E%22%3CSPAN%20class%3D%22line%22%3EAll%20you%20have%20done%20is%20handle%20the%20new%20stub%20format.%20However%20that%20is%20still%20fragile%2C%20and%20will%20break%20in%20the%20future%20if%20it%20changes.%20These%20stubs%20are%20not%20designed%20to%20have%20dependencies%20taken%20on%20it.%3C%2FSPAN%3E%22%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Eand%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%22%3CSPAN%20class%3D%22line%22%3EWhy%20were%20you%20and%20are%20you%20still%20(%3C%2FSPAN%3E%3CA%20href%3D%22https%3A%2F%2Fchromium.googlesource.com%2Fchromium%2Fsrc%2F%2B%2F034bd64db1806d85b2ceacc736074ac07722af4a%255E%2521%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fchromium.googlesource.com%2Fchromium%2Fsrc%2F%2B%2F034bd64db1806d85b2ceacc736074ac07722af4a%255E%2521%2F%3C%2FA%3E%3CSPAN%20class%3D%22line%22%3E)%3C%2FSPAN%3E%3CSPAN%20class%3D%22line%22%3E%20relying%20on%20undocumented%20Windows%20internals%20in%20Chrome%3F%20This%20is%20very%20hacky%2C%20unmaintainable%2C%20and%20leads%20to%20future%20incompatibilities.%3C%2FSPAN%3E%22%3C%2FP%3E%3C%2FLINGO-BODY%3E
Bdsrev
Contributor

Hi, I'm really loving the new Edge (already some noticeable improvements over Chrome!) but I hope the Edge team will take a look at a couple of issues, specifically this one (I know it's marked as Fixed but I know many that would differ) https://bugs.chromium.org/p/chromium/issues/detail?id=522201

 

Also, there are a number of v-sync issues with Chromium on Windows, some of them are listed here https://www.vsynctester.com/chromeisbroken.html

3 Replies
Edge collects crash data using the crash reporting system. Can you please be precise about the set of repro steps you're using that cause Edge to crash, and what version of Edge and Windows you are running?

@ericlaw 

 

Sorry I should made been more clear. They did kinda fix that issues years ago but if you take the time to read through that issue report, I think you'll agree that some changes need to be made there (I'll just paste one of the comments from it: "You are relying on the System Service Call Stub ASM layout on the 64bit kernel. That is beyond wrong. Why are you relying on that? It is incredibly fragile and hinders Microsoft's ability to innovate." )

@ericlaw 

more

"All you have done is handle the new stub format. However that is still fragile, and will break in the future if it changes. These stubs are not designed to have dependencies taken on it."

 

and

 

"Why were you and are you still (https://chromium.googlesource.com/chromium/src/+/034bd64db1806d85b2ceacc736074ac07722af4a%5E%21/) relying on undocumented Windows internals in Chrome? This is very hacky, unmaintainable, and leads to future incompatibilities."

Related Conversations
Tabs and Dark Mode
cjc2112 in Discussions on
17 Replies
Stable version of Edge insider browser
HotCakeX in Discussions on
35 Replies
flashing a white screen while open new tab
cntvertex in Discussions on
11 Replies
How to Prevent Teams from Auto-Launch
chenrylee in Microsoft Teams on
28 Replies