We want to acknowledge some issues you may currently be experiencing on the Virtual Tabletop and ensure you know that we’re following along on social media and our forums, we’re working through the issues, and we hope to have fixes ready for you soon. Memory Error Starting around August 23 we were beginning to get sporadic reports of an “Aw, Snap!” memory error from users and staff. It’s not easy to replicate outside of real play, but it has been our primary focus this week as we narrow it down and push a number of smaller fixes to make the VTT more performant. We’re still investigating this overarching problem and have resolved a number of smaller performance issues along the way, with more to come. If this issue happens, you should be able to refresh your browser to resolve, and no data will be lost from your game. If this error continues, first please write into the Help Center with the following information: A link to the game Has this error occurred more than once in this game? Does the error occur immediately or after some time (or particular actions) in-game? Browser and version Any extensions enabled in your browser Is Hardware Acceleration on or off? Operating System and version CPU, RAM, GPU Disabling browser extensions, changing browsers, and using your browser in incognito mode have all solved this issue in testing. It’s worth noting that we have not found a correlation between a single release and this surge in errors, but have found a number of small performance-related improvements we can make on the VTT. We’re making those changes. EDIT 9/8/22: We've now pinpointed that the issue is specific to an update to the Chrome browser; the issue does not occur on versions equal to or lesser than 103.0.5060.0. The stable release which began to exhibit the tab crashing began rolling out to Chrome users approximately mid-July. Given the way Chrome does phased rollouts, it has taken some time to propagate, which is why reports didn't begin to properly surface until mid-August. We're working to resolve with Google. In the interim we recommend switching to Firefox if you are experiencing this error (typically only GMs), and we will update here when fully resolved. EDIT 9/27/22: We expect a fix from Google on this issue in the next two weeks. Token Bar Issues There’s another raft of issues that primarily revolve around the token bar overlay, which we updated two weeks ago. We updated the token bar overlay to use HTML/CSS, which is going to enable a lot of fun features in the future and also should speed up token bar performance in the long-term. Doing so was part of enabling the hover nameplates and token bar overlay project, which we pursued as part of finishing five of the top 10 Suggestions & Ideas suggestions this year. We released those changes on August 25. In the days following we solved the following emergent and quick-to-solve issues, which were reported on the forums: Changing the color of the token bar overlay now updates the color without requiring a refresh or token movement. Fixed an issue where token bar overlay and nameplates were visible through Fog of War. Fixed an issue with uploading a new PDF or image assets via drag-and-drop. Fixed an issue preventing token names and bars from being seen on pages with dynamic lighting enabled while multiple tokens were selected. Fixed an issue which required players with control over a token to also have “see” enabled in order to see the token bar overlay. For tokens on the dynamic lighting layer, token bar overlay is no longer visible while on other layers. Fixed an issue causing token lag when using Fog of War. (EDIT 9/14) We have released the following fixes today: Fixed a "phantom token" issue where tokens that had drag-and-dropped incorrectly or suffered another error were still showing token bars despite users being unable to interact with them. Fixed an issue where auras were not obeying see/edit rules. Fixed an issue where token bars were no longer allowing "0" as a maximum value. (EDIT 9/29) We have released the following fixes today: Fixed an issue where the opacity of the token bar overlay and nameplate were not matching the opacity of the token image on the GM layer. Fixed an issue where token bar overlay displayed on Map layer. Fixed an issue with the text shadow when zoomed in on token bars. These are the known issues that we’re going to continue working on in the coming weeks, and that you will find updates for in the Change Log as they pass through development, into quality assurance, and eventually into your hands. This list is roughly in the order we’ve prioritized these fixes based on number of reports, usage, and impact, but they may not come out in this order depending on development and QA needs: Opacity on the GM layer should be set on the nameplate and token bar overlay. EDIT 9/29: Done Token bars and nameplates should be hidden on the map layer. EDIT 9/29: Done Token nameplates change after a bubble attribute is edited. EDIT 9/12: See Unrelated Token Issues Selection cursor inconsistency when hovering over a token. Token bar overlay does not respect “Is Drawing.” EDIT 9/12: We may update this in the future but can confirm this functionality is operating as it was prior to any changes. The stroke on the text bar shadow needs to be adjusted slightly. EDIT 9/29: Done Unrelated Token Issues Our changes revealed a larger, pre-existing issue: phantom tokens. These are tokens that are unselectable—and always have been, invisibly lurking on the VTT due to an error when performing a drag-and-drop action or similar. However, with the recent update, these phantom tokens now have bars, making them a visual annoyance. It’s difficult to isolate these tokens from normal tokens and difficult to QA at scale, so a sweep to delete all phantom tokens across all games has a high risk of causing damage to user data. We’re considering options of letting you clear these tokens with a button from within your game, but for now if you are experiencing phantom tokens you can either make a copy of your map without duplicating tokens (Gauss has detailed steps here ) and then re-add any tokens needed or follow the steps outlined by Keith Curtis (requires a Pro subscription). EDIT 9/13, 9/14: We've discovered a temporary for this that will give users a better experience while we determine root cause, and it is live as of 9/14. (EDITED 9/12) There are two other known issues that was not caused by this update but do need a fix: 1) when users change an attribute connected to the token bar, if you don’t load the character sheet before you drag-and-drop a fresh token it shows the default (max) value rather than the changed value. 2) Adjusting linked attribute bubbles renames token. These are an unintended side effect of the big performance improvements we made earlier this year to load 95% of games up to 50% faster , and can be solved individually by updating the value on the character sheet, token settings, or the token itself. I want to thank our forum champions for being on top of reports and helping all of you solve the issues here, especially Gauss, The Aaron, and Keith Curtis. We really appreciate the time and care our forum champions put into the forums and the immense amount of knowledge and experience you all have. We’re sorry for any impact this has had on your games. We hope that the current bugs are those you can work around, and please report anything that isn’t on this list to the Help Center .