Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Browser taking a lot of cpu with lots of connections and then crashes #2517

Open
alban opened this issue May 11, 2017 · 4 comments
Open

Browser taking a lot of cpu with lots of connections and then crashes #2517

alban opened this issue May 11, 2017 · 4 comments
Labels
chore Related to fix/refinement/improvement of end user or new/existing developer functionality component/ui Predominantly a front-end issue; most/all of the work can be completed by a f/e developer performance Excessive resource usage and latency; usually a bug or chore
Milestone

Comments

@alban
Copy link
Contributor

alban commented May 11, 2017

Capturing comment from #2507 (comment):

I tried to quickly create plenty of connections to nginx on several cpus with this script (in several terminals):

sudo docker run -d nginx
cpu=0
for i in $(seq 1 10000) ; do
  echo -n "$i "
  taskset --cpu-list $cpu wget -O /dev/null http://172.17.0.2 2>/dev/null
done
echo

And I didn't notice any problems in the logs of Scope.

However, chrome quickly took all the cpu and crashed:

chrome-crash

/cc @2opremio

@2opremio
Copy link
Contributor

I assume 172.17.0.2 is the IP of the nginx container, right?

Also, scope was running with ebpf enabled.

@2opremio 2opremio added component/ui Predominantly a front-end issue; most/all of the work can be completed by a f/e developer performance Excessive resource usage and latency; usually a bug or chore labels May 11, 2017
@2opremio 2opremio added this to the Backlog milestone May 11, 2017
@alban
Copy link
Contributor Author

alban commented May 11, 2017

@2opremio yes and yes. Sorry, I forgot to mention it.

@rade rade added the chore Related to fix/refinement/improvement of end user or new/existing developer functionality label May 18, 2017
@rade
Copy link
Member

rade commented Jul 31, 2017

@alban what browser was this?

@alban
Copy link
Contributor Author

alban commented Jul 31, 2017

@rade it was Chrome.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
chore Related to fix/refinement/improvement of end user or new/existing developer functionality component/ui Predominantly a front-end issue; most/all of the work can be completed by a f/e developer performance Excessive resource usage and latency; usually a bug or chore
Projects
None yet
Development

No branches or pull requests

3 participants