Andres S

My feedback

  1. 8,546 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    815 comments  ·  Public » Performance  ·  Flag idea as inappropriate…  ·  Admin →

    Great performance and user experience remain a topmost priority for us. Application launch time has seen improvements in the recent build. We will continue making improvements across the product including channel to chat switching and overall resource consumption.

    Andres S commented  · 

    Las time @Warren responded was September 9, 2018. That is like 8 months ago. He said several weeks... so what happened?

    Andres S commented  · 

    Hi, well, same here. I started noticing my laptop going full wind blast mode for no reason and traced it to Teams using 100% (of one CPU thread).

    In my laptop's case, that is 12.5% (100% CPU / 4 cores / 2 threads per core = 1 thread running at 100%).

    Going over its execution details on Process Explorer, found that there is one thread which starts at "IsSandboxedProcess+somenumber" and that thread is stuck on "waiting thread sync". That thread had used *a lot* of CPU Process Explorer claims.

    So, this process is stuck on a deadlock situation of sorts, my very rusty developer gut tells me. If that is the case, thats a crass bug.

    Once quit Teams (using its own Quit command), the wind turbine mode on my laptop stopped, almost immediately.

    Once I started Teams, it didn't go CPU crazy. My laptop had just resumed from sleep.

    I have no more time to delve deeper into this, hopefully this information helps - somehow. Teams is quite slow, but now being CPU hog... not good.

    I will cross post this on other threads I find relevants, apologies in advance.

    Andres S supported this idea  · 
  2. 36 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    8 comments  ·  Public » Performance  ·  Flag idea as inappropriate…  ·  Admin →
    Andres S supported this idea  · 
  3. 11 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Public » Messaging  ·  Flag idea as inappropriate…  ·  Admin →
    Andres S supported this idea  · 
  4. 48 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    10 comments  ·  Public » Performance  ·  Flag idea as inappropriate…  ·  Admin →
    Andres S supported this idea  · 
    Andres S commented  · 

    Hi, well, same here. I started noticing my laptop going full wind blast mode for no reason and traced it to Teams using 100% (of one CPU thread).

    In my laptop's case, that is 12.5% (100% CPU / 4 cores / 2 threads per core = 1 thread running at 100%).

    Going over its execution details on Process Explorer, found that there is one thread which starts at "IsSandboxedProcess+somenumber" and that thread is stuck on "waiting thread sync". That thread had used *a lot* of CPU Process Explorer claims.

    So, this process is stuck on a deadlock situation of sorts, my very rusty developer gut tells me. If that is the case, thats a crass bug.

    Once quit Teams (using its own Quit command), the wind turbine mode on my laptop stopped, almost immediately.

    Once I started Teams, it didn't go CPU crazy. My laptop had just resumed from sleep.

    I have no more time to delve deeper into this, hopefully this information helps - somehow. Teams is quite slow, but now being CPU hog... not good.

    I will cross post this on other threads I find relevants, apologies in advance.

    --------------
    leafblower....lol good description.

  5. 1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Public » Performance  ·  Flag idea as inappropriate…  ·  Admin →
    Andres S commented  · 

    Hi, well, same here. I started noticing my laptop going full wind blast mode for no reason and traced it to Teams using 100% (of one CPU thread).

    In my laptop's case, that is 12.5% (100% CPU / 4 cores / 2 threads per core = 1 thread running at 100%).

    Going over its execution details on Process Explorer, found that there is one thread which starts at "IsSandboxedProcess+somenumber" and that thread is stuck on "waiting thread sync". That thread had used *a lot* of CPU Process Explorer claims.

    So, this process is stuck on a deadlock situation of sorts, my very rusty developer gut tells me. If that is the case, thats a crass bug.

    Once quit Teams (using its own Quit command), the wind turbine mode on my laptop stopped, almost immediately.

    Once I started Teams, it didn't go CPU crazy. My laptop had just resumed from sleep.

    I have no more time to delve deeper into this, hopefully this information helps - somehow. Teams is quite slow, but now being CPU hog... not good.

    I will cross post this on other threads I find relevant, apologies in advance.

Feedback and Knowledge Base