#Game closes entire browser after certain amount of time
96 messages · Page 1 of 1 (latest)
could be bcs openfront takes a lot of RAM. if your PC don't have enough ram, especially if you're doing something else on it at the same time, your browser might crash because there's no temporary storage space (RAM) left in your computer.
@dreamy saddle
I have 32 gigabytes of RAM. Wasn't really doing anything else at the time.
was working fine on the last version.
Do you get any errors leading upto the crash?
did another test with console open, it crashes out so fast i cant even see if debug output produces an error, leading up to nothing
im not too familliar with chrome based browsers, is there a way to log the console output?
So the 5-10 minutes it's all fine?
Can you try it on the beta https://beta.openfront.io
@dreamy saddle while you play it, keep a eye on task manager and check if your ram usage spikes as you play
hey - i'm not an expert, and not sure what levels of tech expertise we're talking here, but: (from an LLM, haha):
WHY DevTools cannot auto-save logs (by design)
DevTools is sandboxed inside the tab’s renderer process, and when the tab crashes:
DevTools dies
Console history is lost
No API is available to write to disk
That’s why Chrome’s own engineers say:
“To capture logs during crashes, start Chrome with logging flags.”
i tested, this should work for people:
chrome.exe --enable-logging --v=1
that does write a file:
chrome_debug.log
(under \appdata\local\google\chrome\user Data)
tho i can't attest to its usefulness in this instance
This is an interesting one
testing for debug output, stand by
Presumably this isn't a hardware issue
Can you grab a link to a game where this happened in your browser history?
url of any game should work
active game
singleplayer
im just letting it run
lmk when it ends
ive debugged quite a few programs before and uh... if this is player related i may have to make a new game lol
Honestly the first I've seen this happen
oddly, it happened once before a few months ago but i doubt its related
THERE WE GO
I'll run a game and see if I get comparable output
crashed
last few lines including the critical
[WA]RWADI::NotifyRenderError
wew lad
makes me wonder if its related to nation size
oh thats a fun bug lol
just linking, i remember vaguely from months ago, there was a mini thing about this (should have been solved..at least previous issue)
of course, i lack many details 😂 😭
Try running a game with audio disabled maybe
you mean mute the tab? or an inagme setting?
You have 44GB of pagefile
In game
yes lol, i know what im doing
thats there for a reason
im a developer myself
You can't disable audio it seems, only sliders, so don't think that's it
ah, already setujp that way
This may be one for the GutHib ngl
if i cant sort this yeah, ill post it there
its also happening on the dev site too
Super strange one. All I can think of is some hardware issue, but that doesn't make much sense
Which one?
let me see if i can figure out which one again, i did that test last night
it was a dev site listed on a feature preview
And just to make absolute certain it's not a memory leak, can you check if this keeps climbing?
V23 has not crashed yet, other versions would have
Version specific then, weird
not just that, it was not crashing a week ago
the newer version with the newer sprites worked fine
OH CRAP, NEVERMIND IT DID CRASH
Damnit
so def something on my end
Did you manage to look at this?
Or think it might not be useful
okay, so with stable diffusion ( it was in idle ) shutdown same thing
ive got to go as well, its my fathers birthday
Gotcha, have a good time!
Ping me if you want someone to bounce ideas off
I'm no dev though
issue found, corrupt in memory driver routine
opened yt in edge and same error occurred so i went on a deep dive
( i only use edge for yt sometimes and open front )
restarting pc fixed it
oddest thing ive seen in a good while
this can be closed
Thanks mate!