Gmail and Inbox both hang for me on my Chrome on Linux with almost no load. It's funny how tides turn. Initially Gmail was the king of performance.
What is all this stuff even doing?
11–20 of 320 posts
Gmail and Inbox both hang for me on my Chrome on Linux with almost no load. It's funny how tides turn. Initially Gmail was the king of performance.
What is all this stuff even doing?
“I work on Chrome, on Windows” ... chrome_child.dll (stack base) KernelBase.dll!VirtualAlloc ntoskrnl.exe!MiCommitVadCfgBits ntoskrnl.exe!MiPopulateCfgBitMap ntoskrnl.exe!ExAcquirePushLockExclusiveEx ntoskrnl.exe!KeWaitForSingleObject (stack leaf) So don’t use a proprietary kernel that performs poorly?
I could work on Chrome for Linux, but then this bug on Windows might never get found or fixed. I am satisfied with my choices, despite the occasional glitches.
Gmail and Inbox both hang for me on my Chrome on Linux with almost no load. It's funny how tides turn. Initially Gmail was the king of performance.
I need 27 seconds on Firefox 52.9 ESR (Debian) and about 20,287 kbyte of data transferred in 148 requests just to reach an idle GMail tab. What is all this stuff even doing?
Gmail and Inbox both hang for me on my Chrome on Linux with almost no load. It's funny how tides turn. Initially Gmail was the king of performance.
I need 27 seconds on Firefox 52.9 ESR (Debian) and about 20,287 kbyte of data transferred in 148 requests just to reach an idle GMail tab. What is all this stuff even doing?
So basically it is the problem with CFG (exploit protection) which is not ready for the cases when there are many allocations and freeing of excutable memory blocks.
“I work on Chrome, on Windows” ... chrome_child.dll (stack base) KernelBase.dll!VirtualAlloc ntoskrnl.exe!MiCommitVadCfgBits ntoskrnl.exe!MiPopulateCfgBitMap ntoskrnl.exe!ExAcquirePushLockExclusiveEx ntoskrnl.exe!KeWaitForSingleObject (stack leaf) So don’t use a proprietary kernel that performs poorly?
I'm confused about your suggestion. I work on the Chrome web browser on the Windows platform. If we want to allocate memory we, ultimately, need to call VirtualAlloc. I could work on Chrome for Linux, but then this bug on Windows might never get found or fixed. I am satisfied with my choices, despite the occasional glitches.
“I work on Chrome, on Windows” ... chrome_child.dll (stack base) KernelBase.dll!VirtualAlloc ntoskrnl.exe!MiCommitVadCfgBits ntoskrnl.exe!MiPopulateCfgBitMap ntoskrnl.exe!ExAcquirePushLockExclusiveEx ntoskrnl.exe!KeWaitForSingleObject (stack leaf) So don’t use a proprietary kernel that performs poorly?
Gmail and Inbox both hang for me on my Chrome on Linux with almost no load. It's funny how tides turn. Initially Gmail was the king of performance.
Gmail and Inbox both hang for me on my Chrome on Linux with almost no load. It's funny how tides turn. Initially Gmail was the king of performance.