Roll20 uses cookies to improve your experience on our site. Cookies enable you to enjoy certain features, social sharing functionality, and tailor message and display ads to your interests on our site and others. They also help us understand how our site is being used. By continuing to use our site, you consent to our use of cookies. Update your cookie preferences .
×
May your rolls be chill this holiday season!
Create a free account

Crash: Chrome/Win7-64

I am entirely unable to run the program in Chrome. It crashes every time I try to interact with the virtual table. I have Win7-64bit SP1, intel 2600K, 8GB RAM, Chrome version 19.0.1084.52 m, updated flash and shockwave. It works fine in Firefox 12.
The devs have unfortunately gone to bed, but I'll make a note for them to take a look tomorrow and get back to you tomorrow.
Just would like to say I am also having this issue.
Just checking in on this -- can you guys take a look at this article and make sure you're only running one version of Flash? <a href="http://www.howtogeek.com/103292/how-to-fix-shockwave-flash-crashes-in-google-chrome/" rel="nofollow">http://www.howtogeek.com/103292/how-to-fix-shockwave-flash-crashes-in-google-chrome/</a> I know it seems unrelated, but I honestly have no idea what else could be causing this, since that's a system-level error message Chrome is throwing, which isn't one you can typically cause just by calling Javascript...
I'll try and take a look tonight when I get home, will let you know!
It took me forever but I was able to get it to work with that advice. Now the only problem is when I start up my campaign page I get a yellow box at the top of my screen saying "adobe flash player was blocked because it is out of date" and nothing will work unless I click the "run this time" option. I don't understand why it would work after activating flash from that screen instead of keeping it on but what you gonna do. Either way it works finally. Thanks for the help. (First time actually using Google chrome if you cant tell xD)
Yup - that fixed it! Very non-intuitive. Thanks Riley!