Hi everyone,
I would like to share some updates about some of the ongoing performance
related work.
We have started looking at the native stack traces that are submitted
through telemetry from the Background Hang Reports that take more than 8
seconds. (We were hoping to have been able to reduce
Can confirm for Ryzen: FWIW, my stock R7 1800x (RAM @2133Mhz for now
:( ) did a Windows debug clobber in 15:32.40 with the default -j16.
(any directory that showed up as read by MsMpEng in Resource Monitor
excluded for Defender)
I'll give it a run through with Defender disabled, and see if there's
On Thu, Apr 20, 2017 at 11:13 PM, Bevis Tseng wrote:
>
>
> On Thu, Apr 20, 2017 at 10:15 AM, Bevis Tseng wrote:
>
>> A soft reminder of using AbstractThread::GetCurrent()/MainThread()
>> after some design change for Quantum-DOM.
>>
>> If this message/callback is to be handled on *the main thre
On Thu, Apr 20, 2017 at 10:15 AM, Bevis Tseng wrote:
> A soft reminder of using AbstractThread::GetCurrent()/MainThread()
> after some design change for Quantum-DOM.
>
> If this message/callback is to be handled on *the main thread of the
> content process*, please use the replacement called Ab
On 04/20/2017 05:15 AM, Bevis Tseng wrote:
A soft reminder of using AbstractThread::GetCurrent()/MainThread()
after some design change for Quantum-DOM.
If this message/callback is to be handled on *the main thread of the
content process*, please use the replacement called AbstractMainThreadFor
5 matches
Mail list logo