An unnecessary trace log is output in the latest version of Spector.js

[cx20]

I discovered that unnecessary trace logs will appear in the latest version of Spector.js.
Relate: #35

OS / Browser : Windows 10 + Chrome 58 + Spector.js v0.2.1

How to reproduce the problem:

1. Install Spector.js from the Chrome Web Store.
   https://chrome.google.com/webstore/detail/spectorjs/denbgaamihkadbghdceggmchnflmhpmk
2. Please access the WebGL sample page with Chrome.
3. Start the Spector.js extension from the toolbar.
   
   Unnecessary trace log (glp -> [object Object]) seems to be outputted.
   

[sebavan]

Seems to be linked to the fact that other extensions are also tracking the context (probably weblglinsight) I need to figure out how to split between the real log and the other extensions commands.

[cx20]

I confirmed that the path output to Stack Trace matches the ID of WebGL Insight.

Stack Trace
0: WebGLRenderingContext.default (chrome-extension://djdcbmfacaaocoomokenoalbomllhnko/src/content_script/fcn_bindings.js:7:12)
1: WebGLRenderingContext.drawElements (chrome-extension://djdcbmfacaaocoomokenoalbomllhnko/src/content_script/webgl_bind.js:10:24)
2: WebGLRenderingContext.drawElements (<anonymous>:1:96314)
3: h.draw (http://jsrun.it/assets/3/W/f/g/3WfgZ:4:8704)

I tried to disable the "WebGL Insight" Chrome extension, and unnecessary trace logs are no longer output.

[sebavan]

@cx20 I am still trying to figure the best approach concerning this issue.

[sebavan]

Explicitly removed those internals commands.