-
Notifications
You must be signed in to change notification settings - Fork 175
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Out of Memory #813
Comments
Very similar: #100 |
It is, but mine actually gave a crash bit of information and asserted that itself was attempting to allocate way too much memory. |
We've been running valgrind runs and long-term runs and we haven't found anything too terrible. We definitely leak memory but it's a few megabytes and no ever-increasing leaks, nor have we seen the client crash when running long-term. It may have been something that was introduced and then fixed or something configuration dependent, like a driver leak. We'll have to keep an eye out. |
I've also had this issue, running steam for just a few hours caused it to run out of memory. I have 4GB of RAM and 4GB swap on my system, and wasn't using very much of it. Pretty odd that it would run out of memory so easily though, given how virtual memory works.
System specs: http://paste.strictfp.com/36447 Edit: Resuming a download seems to cause virtual memory to go up by 1 mb/s |
Like tiffany352 I have seen this multiple times while in the process of downloading large games over a small network pipe (e.g., 10GB of TF2 over 1.5Mb/s DSL). To the best of my knowledge, I haven't seen it while a download was not active. |
After running for only 2-3 hours I got a OOM too. I tried to click on the fresh installed Beat Hazard in my library, which seemed to trigger the fault. I have 16 GB of RAM btw ;)
|
I have a more impressive/worrying OOM crash, asking for a few GB:
Steam was in the background, downloading Killing Floor, doing nothing else ‐ https://gist.github.com/johndrinkwater/5012668 |
No games or any other Steam-related processes were running, it was just the client doing a download? The allocation is coming from an inter-process communication request and it looks like the request was garbage or was turned into garbage (can't tell from the failure report). Nobody else in the process appears to be making a request, though. |
Sorry for posting this twice, but as Mr. Schism had pointed out, I had posted this in a closed bug and it's probably better to post my updated details here. It just occurred to me that I likely had the "Downloads" window open in steam while Killing Floor was downloading. My steam memory usage is at ~1.2GB right now and rising, and my "String Page Texture" sizes are rising. I'm ignorant as to what those are but they growing as high as 18MB. The following is being printed to stdout: roaming config store 2 saved successfully Could this be the memory leak? On the downloads window: I'm now at ~1668MB and growing while on that screen. |
@gdrewb-valve no game, though I guess I did have a minimised Steam chat window. |
Thanks for the additional info. @KungFuJesus , how quickly is the memory usage growing? I've been playing around with setting up multiple downloads and then watching the downloads page but 'top' doesn't report any significant growth over a period of ten minutes or so. If you try that how quickly does it grow for you? |
This crash happened to me also, But actually I cannot know at what time exactly did it crash. As I left it downloading Team Fortress 2 and went to sleep then next day I found it crashed with the nearly the same lines as in the first post. Video Card: Intel & Nvidia GT 525M |
At that time it was about a MB every couple of seconds or so. I just ran it again on the download screen and it seems to be growing at the same rate after the notifications for the updates to TF2 were done downloading. I'm now at 892MB. I understand steam does some IPC, right? adam@eggsbenedict ~ $ ipcs ------ Shared Memory Segments -------- ------ Semaphore Arrays -------- ------ Message Queues -------- My /tmp where the FIFO for steam resides is a tmpfs mount, could that have anything to do with it? If there was a way for me to collect a coredump and host it somewhere would this be useful to you? |
This also may be useful before it crashes: adam@eggsbenedict ~ $ ps -ef | grep steam adam@eggsbenedict ~ $ lsof -p 15306 |
I'm still not seeing any significant leaking, so we need to try and pin down what's different between us. First, the minimal steps to get to the point that it leaks. If you switch to your library, then completely shut down Steam and restart and get back to your library (assuming no updates or games download) does it start leaking when displaying your library? If you start downloading a game buffers will be allocated and memory use will increase, but when the download stops that should go steady-state. Does it continue to increase after that? At what rate? |
I have this error too. Seems to happen when I'm AFK for a few hours. |
Running Steam on ubuntu 12.10 64-bit (steam:29242): Gtk-WARNING **: Unable to locate theme engine in module_path: "oxygen-gtk", (steam:29242): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're it's parent. (steam:29242): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're it's parent. (steam:29242): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're it's parent. (steam:29242): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're it's parent. (steam:29242): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're it's parent. (steam:29242): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're it's parent. (steam:29242): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're it's parent. (steam:29242): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're it's parent. (steam:29242): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're it's parent. (steam:29242): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're it's parent. (steam:29242): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're it's parent. (steam:29242): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're it's parent. Assert( Fatal assert ):/home/buildbot/buildslave_steam/steam_rel_client_ubuntu12_linux/build/src/tier0/memstd.cpp:2501 Installing breakpad exception handler for appid(steam)/version(1361807486_client) looks like the dump was uploaded. very similar error: left the client to download TF2 overnight and it crashed due to some kind of memory error. smells like a leak to me. I don't think the GLIB warnings are related - they are likely there because of differences in Xmonad. |
Completely removed steam and reinstalled it, don't seem to be having issues anymore. I initially had been running it straight out of my home directory after it was unpacked from the .deb, but using what my distro provides from a fresh start seems to have made this issue disappear. I'm also not using STEAM_RUNTIME anymore and using the libraries my distro provides, maybe that has something to do with it. |
I doubt the Steam Runtime has anything to do with it; this issue started up before the runtime was released (I think). I haven't installed a large enough game to get this to happen lately, though I suspect wifi may be partly to blame based on some discussions I've had and some reading I've done. I've had a few people say that this occurred when their wifi dropped out for a short time (which can happen without even noticing). @Ben64 , @maxdeliso , and @KungFuJesus : Are any of you guys using wifi? |
@MrSchism not me. |
@MrSchism Nope, 100mbit through switch to router. It just crashed again, coming out of screensaver. |
Just had it happen again (TF2 reinstall). This time it crashed, even without going into a locked or suspended state. I actually watched it throw the error and shut down. Gist of the crash located here: https://gist.github.com/MrSchism/c1f1ede305de7feafbec |
Same happens to me after steam launching but only if connected to internet. In offline mode steam doesnt crashes. UPD: very unstable, sometimes it starts. |
For what it's worth when it happened to me most recently, I had actually recently upgraded and this was a reinstall. I now run a 2.9 Ghz quad-core with 12 GB RAM... Wonder if it's using a buffer or swap more than RAM. |
I'm still getting this after long periods of idling. |
still getting it |
it seems the issue is fixed with some of the latest steam updates. |
I made a script to log the output of "ps aux" for the steam process every minute. Looks like it crashes when it reaches about 4GB of memory. USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND |
IIRC, I have this problem forever. Steam randomly crashes with no obvious reason, what ever I do: play some game, trade or just reading Reddit with client active in background. Crash log obtained from terminal is extremely simular to one in issue description:
2097152 in description is 2 GiB in bytes (according to attached specs, they have 2 GB), while my 4194304 is equal to 4GiB, exactly amount of RAM installed. I now have 8GiB and Steam just crashes, without any info about allocating memory.
Valve should really look into it :/ I'm not very familiar with GitHub and ticket management, please tell me if I need specify something else (e.g. I can attach dumps). |
I am also having this issue, while downloading X3: TC. It seems to have caused a game of Don't Starve to crash along with it, but it also happens when I just leave Steam running while downloading. |
strange that for me this issue just dissapeared about month ago and havent happened since then. |
I just ran into this issue. I did notice that steam had been taking up about 3gB of ram (I have 20gB in my system) before I got the error - Assert( Fatal Assertion Failed: OUT OF MEMORY ) - I wasn't doing anything out of the ordinary. |
Has anybody seen this with recent beta Steam releases? |
no. this havent been an issue for quite some time at least for me. |
Thanks, closing until a new repro is found. |
Steam is running "out of memory" for me right on startup. I have 16G memory + 32G swap.
|
System Specs: https://gist.github.com/45ed161ede54ebc30909
So last night, I decided to lock my computer and head to bed. I did't put it in sleep or suspend because it's a desktop and there's really no reason to do so.
I know that locking the screen hasn't disconnected me before (being I lock it every time I walk away from it).
I return to it in the morning and Steam isn't running. I look at my terminal output and see the following:
The text was updated successfully, but these errors were encountered: