Portal level numbers plugin with too many portals crashes chrome and chromium

[maugsburger]

It looks like there is a problem with the portal numbers plugin, at least after the last chrome/chromium update I did (so perhaps it's a browser bug, as it didn't show up with the previous chrome/chromium version and same IITC version).

Steps to reproduce: Have IITC and Portal Level numbers plugin active, open an area with many portals (eg https://www.ingress.com/intel?ll=49.007869,8.408146&z=13) and wait. The portals/links/fields are drawn fine, but about half the way of filling the portals with their level numbers the window crashes. Aw, Snap!

I can't see any problem inside the JS console:

Tampermonkey started VM90:52
Loading included JS now VM103:1293
Consider using 'dppx' units, as in CSS 'dpi' means dots-per-CSS-inch, not dots-per-physical-inch, so does not correspond to the actual 'dpi' of a screen. In media query expression: (min-resolution: 144dpi) VM103:1820
Consider using 'dppx' units, as in CSS 'dpi' means dots-per-CSS-inch, not dots-per-physical-inch, so does not correspond to the actual 'dpi' of a screen. In media query expression: (min-resolution: 144dpi) VM103:1821
done loading included JS VM103:10979
GET https://ssl.google-analytics.com/__utm.gif?utmwv=5.5.3&utms=40&utmn=1543877…com%7Cutmccn%3D(referral)%7Cutmcmd%3Dreferral%7Cutmcct%3D%2Furl%3B&utmu=q~ net::ERR_BLOCKED_BY_CLIENT ga.js:63
GET https://ssl.google-analytics.com/__utm.gif?utmwv=5.5.3&utms=41&utmn=1837578…com%7Cutmccn%3D(referral)%7Cutmcmd%3Dreferral%7Cutmcct%3D%2Furl%3B&utmu=6~ net::ERR_BLOCKED_BY_CLIENT ga.js:63
loading done, booting. Built: 2014-07-05-043348 VM103:1149
starting map refresh in 3 seconds VM103:13520
mappos: reading cookies VM103:12534
refresh map movestart VM103:13464
cancelling existing map refresh timer VM103:13511
starting map refresh in 3 seconds VM103:13520
refreshing chat VM103:11447
Render: deleted 0 portals by level VM103:12879
Render: map zoom 13 changes portal scale to 0.8 - redrawing all portals VM103:13214
requesting data tiles at zoom 13 (L2+ portals, 6500 tiles per global edge), map zoom is 13 VM103:13607
done request preparation (cleared out-of-bounds and invalid for zoom, and rendered cached data) VM103:13683
7
getThinnedEntities status: 4 tiles: 4 successful, 0 timed out, 0 failed. delay 0.05 seconds VM103:13899
finished requesting data! (took 10.808 seconds to complete) VM103:14015
starting map refresh in 300 seconds VM103:13520

google-chrome-stable: Installed: 36.0.1985.125-1 chromium: Installed: 36.0.1985.125-0 IITC 0.17.3.20140705.43348 IITC plugin: Portal Level Numbers 0.1.4.20140705.43348

all on Debian testing/x64

It feels like the provided data is not comprehensive enough to nail down the crash's cause, so please tell me where to gather further information, I'm not that familiar to (in-)browser debugging.

[ramereth]

I'm experiencing the same issues and can confirm the problem goes away if I disable that plugin.

google-chrome-stable: Version 36.0.1985.125 Ubuntu 12.04 x86_64 IITC 0.17.4.20140727.231704 IITC plugin: Portal Level Numbers 0.1.4.20140705.43348

Let me know if I can provide any further data.

[jonatkins]

Well I don't see how a plugin that just adds some HTML

entries could crash the browser, unless the browser, or related component, has a bug.

As this hasn't been widely reported, one possibility would be a graphics driver issue. The answer to this post - http://superuser.com/questions/606578/how-can-i-disable-accelerated-compositing-in-chrome-without-relying-on-a-shortcu - suggests a couple of flags that can be changed in chrome that might help.

Also, check to see if your graphics drivers are out of date.

[skyluc]

I had this problem and found this bug report. It made me check my graphic driver. And as it was a freshly installed Ubuntu-64 14.04.01, it was still using a generic driver. I updated to the 'current' nvidia binary driver. And it solved the problem.

So in my case, it was a problem with the graphic driver.

[shewitt]

+1 for that. Switching to the Nvidia binary driver (331.38) instead of Nouveau on Ubuntu 14.04 fixed this.