JavaScript is required to use Bungie.net

Forums

5/31/2015 2:48:07 PM
5
hey i don't know if this will help you but i was messing around with a bunch of things like turning webgl support on and off and the site was still crashing then tried using experimental webGL protocols still crashed so then i started messing with my display settings and low and behold that seemed to do the trick, i changed my recommended (1366 x 768) display resolution to the highest resolution available on my chrome book (1536 x 864) bungie.net seems much more stable now especially while viewing items and gear in the legend tab, try changing your display settings i hope it works for you too.. carry on the fight good luck guardian..
English

Posting in language:

 

Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

  • Thanks for the tip!

    Posting in language:

     

    Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

  • my chrome book still crashes but not as quickly as before, but it still really sucks, came across this crash report on the internet for google chrome they think its bungie's fault it crashes on chrome https://code.google.com/p/chromium/issues/detail?can=2&start=0&num=100&q=label%3ACr-Blink- WebGL&colspec=ID%20Pri%20M%20Week%20ReleaseBlock%20Cr%20Status%20Owner%20Summary%20OS%20Modified&groupby=&sort=&id=492411

    Posting in language:

     

    Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

  • DO NOT CLICK THE LINK copy and paste the whole thing in your browser to view a google chrome crash report

    Posting in language:

     

    Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

  • The problem's almost certainly caused by the fact that their character viewer isn't using vertex attribute 0; there are hundreds of warnings about this in the JavaScript console. This causes Chrome to go down a slow path which may be triggering a graphics driver bug. I can reproduce the slowdown on my MBP Retina, but not a desktop Mac Pro with AMD Radeon HD 7950 graphics card. I'll try to figure out what Chrome's GPU resource allocation pattern is for this situation. Going forward, the WebGL 2.0 implementation will necessitate Chrome using the OpenGL Core Profile on Mac OS X, which doesn't require this emulation. In Chrome Canary, passing the command line argument --enable-unsafe-es3-apis already avoids this bad behavior.

    Posting in language:

     

    Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

  • Repro: 1. Load page 2. Click around on some of the gear inventory icons 3. Await doom Symptoms observed: Interactions are quick at first, then slow to a crawl. Waiting on the page for a while (~1min) caused a kernel panic. The info below is from the Apple kernel crash-recovery dialog on the next boot // Begin Apple crash report

    Posting in language:

     

    Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

You are not allowed to view this content.
;
preload icon
preload icon
preload icon