Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs

No Crypto For Old Men 7DRL

Hack servers and steal data in this HTML5 roguelike game. · By Lone Spelunker

Crash bug

A topic by Edwin DeNicholas created Mar 14, 2016 Views: 308 Replies: 4
Viewing posts 1 to 3
(1 edit)

I hate to be the bearer of bugs again, but I've been playing a bunch and well, every 20-30 minutes or so (haven't actually timed it) the tab the game is running in will crash. This seems to happen regardless of what I'm doing in the game, even just idling it will happen. I've been saving my progress often so it's not the worst thing. I'm using Chrome on Windows 10. On the plus side, I'm making good progress tracking down my brother, just need to find a .lnk to a particular server...

Developer

Wow, sorry about that. Thanks for reporting this; I'll see if I can figure out what's up. I'm pretty sure it's platform-specific, since I've had the game running for many hours at a time in browser tabs without a crash on my development machine, so it might take some time to track it down. If you notice a pattern or see any error messages that might shed light on what's causing it, let me know. Thanks!

There's also another weird bug where if you have the lnk file for the first phone quest, leaving via any exit node kills the game by putting you in a limbo state where you cannot interact with the world.

Developer

I just uploaded a new version of the game that fixes some bugs.  Can you try it out and see if it works better for you now?

(1 edit)

I'm also seeing Chrome crash on Windows or on ChromeOS, after maybe 30-45 minutes of play (although it happened once after less than 10 minutes), on both the 7DRL version and the current release. The entire renderer tab is dying, which suggests out-of-memory or a browser bug.

The tab can sit there unplayed for a day or more, so it's not a steady-state memory leak, but something triggered by interaction.

Taking memory snapshots using Chrome DevTools, the javascript heap is growing around 300-600 kb per exit node transited; that's shouldn't be enough to crash the renderer unless you're hacking hundreds of networks.