Google Chromium Bug: Huge amount of goats teleported(code.google.com)
code.google.com
Google Chromium Bug: Huge amount of goats teleported
http://code.google.com/p/chromium/issues/detail?id=31482
7 comments
The comments are priceless.
either bug or egg, but it realy teleports goats too fast.
What are ewe guys bleating about?
This comment by [email protected] makes me think there's a puzzle to be solved here:
The teleportation rate is actually a linear function of the number of tabs you have open. Each tab has to teleport a certain number of goats to operate, although as dank points out we were able to optimize it during the Linux port and reduce the number of goats required. I have some further optimizations in mind if we'd like to reduce it more to address the issue mentioned in comment #11.
Without looking at the code, what could that column really be measuring?
The teleportation rate is actually a linear function of the number of tabs you have open. Each tab has to teleport a certain number of goats to operate, although as dank points out we were able to optimize it during the Linux port and reduce the number of goats required. I have some further optimizations in mind if we'd like to reduce it more to address the issue mentioned in comment #11.
Without looking at the code, what could that column really be measuring?
My guess was that it was some kind of count of the number of messages passed between the different chrome processes - but it probably grows way too fast for that to be the case.
I found this post: http://www.sorcerers-isle.net/article/goats_teleported.html which does take a look at the source code. Although that doesn't reveal the intention behind the counter, my guess is that it was perhaps done to test the updating of the task manager.
I found this post: http://www.sorcerers-isle.net/article/goats_teleported.html which does take a look at the source code. Although that doesn't reveal the intention behind the counter, my guess is that it was perhaps done to test the updating of the task manager.
// See design doc at http://go/at-teleporter for more information.
I believe //go/... is an internal Google URL. The plot thickens!
I believe //go/... is an internal Google URL. The plot thickens!
Since it says "each tab has to teleport a certain number of goats to operate," I speculate that it has something to do with monitoring the performance of the tabs, or maybe just the tabs reporting their memory/cpu/traffic back to the master process.
If mdm truly knows what the code does, and if a browser _has_ to do it, maybe if a browser doesn't send it's statistics back, or poll the main process, then it is declared unresponsive.
If mdm truly knows what the code does, and if a browser _has_ to do it, maybe if a browser doesn't send it's statistics back, or poll the main process, then it is declared unresponsive.
Developers should know better than to use a GET request for teleportation.
Aww it doesn't work in Chromium 3 :(