• Recent
  • Tags
  • Popular
  • Home
  • Docs
  • Register
  • Login
RetroPie forum home
  • Recent
  • Tags
  • Popular
  • Home
  • Docs
  • Register
  • Login
Please do not post a support request without first reading and following the advice in https://retropie.org.uk/forum/topic/3/read-this-first

DRM_IOCTL_MODE_CREATE_DUMB failed: Cannot allocate memory

Scheduled Pinned Locked Moved Help and Support
memoryraspbianbusterlaunch gamepi4 b
44 Posts 9 Posters 10.5k Views
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • R
    roslof
    last edited by 20 Jan 2020, 02:52

    I let my system "soak" for 5 hours and it eventually froze on a black screen. I looked into it and learned that the video screensaver has a separate option for using OMX. Since it was using libVLC, memory was maxed in ES -- thus the freeze.

    I set the screensaver to use OMX for videos, then started a new soak test. I noted the screensaver videos don't render w/OMX enabled. Perhaps I'm missing something in configuration.

    Not clear is this a known issue and if there is a work-around...

    R 1 Reply Last reply 20 Jan 2020, 03:04 Reply Quote 0
    • R
      roslof @roslof
      last edited by roslof 20 Jan 2020, 03:04

      Ah... Looks like if OMX is set, and "Show Game Info On Screensaver" is set to anything other than Never, the videos won't render. So for now, I've disabled overlaying game info.

      Re-running soak test with OMX enabled...

      M 1 Reply Last reply 20 Jan 2020, 04:39 Reply Quote 0
      • M
        mitu Global Moderator @roslof
        last edited by 20 Jan 2020, 04:39

        @roslof on the Pi4, omxplayer can't render the subtitles - it's not supported. Maybe we need that taken care of in EmulationStation.

        I've set the EmulationStation screensaver since my last reply, so it's been running for about 7 hours, but there's no crash and the memory has stayed the same (from what top tells me).

        I'll see if using the theme and doing the switch as you mention would make EmulationStation crash.

        R 1 Reply Last reply 20 Jan 2020, 17:15 Reply Quote 1
        • R
          roslof @mitu
          last edited by 20 Jan 2020, 17:15

          @mitu for me without omx, memory creeps regardless of theme. Even Carbon. Maybe there is something out of date with my setup. Can't imagine what. Will keep looking.

          1 Reply Last reply Reply Quote 0
          • M
            mitu Global Moderator
            last edited by mitu 20 Jan 2020, 17:19

            Can you try to reproduce the crash again, then attach the dmesg output on pastebin.com ? Just redirect to a text file, then upload the file there:

            dmesg > ~/roms/dmes.txt
            

            Preferably after a reboot, just fiddle with EmulationStation 'till crashes, then get the log.

            R 1 Reply Last reply 20 Jan 2020, 20:17 Reply Quote 1
            • R
              roslof @mitu
              last edited by 20 Jan 2020, 20:17

              @mitu no trouble.

              Here is the output (omx off, reboot, navigating ES w/Hursty's Magazine Madness theme - no game launching)

              https://pastebin.com/vNpii7wW

              G 1 Reply Last reply 28 Dec 2020, 05:44 Reply Quote 0
              • M
                mitu Global Moderator
                last edited by mitu 20 Jan 2020, 21:17

                Yep, it's the OOM killer alright, indicative of a memory leak or an over-commit situation.
                What's your allocated VRAM in EmulationStation ?

                R 1 Reply Last reply 20 Jan 2020, 21:46 Reply Quote 0
                • R
                  roslof @mitu
                  last edited by 20 Jan 2020, 21:46

                  @mitu I've played with 200-250MB. Happy to ramp it further if it prolongs the crash.

                  S 1 Reply Last reply 2 Oct 2020, 12:43 Reply Quote 0
                  • R
                    Retropia.rd
                    last edited by 27 May 2020, 14:58

                    Hi all, I found out that the problem occurs when the RPi4 is configured to display 4K. If you change the /boot/config.txt and force 1080p, the problem goes away.

                    1 Reply Last reply Reply Quote 0
                    • S
                      shavecat
                      last edited by 8 Jun 2020, 21:50

                      Hey im having the same here any ideas ?

                      B 1 Reply Last reply 9 Jun 2020, 00:47 Reply Quote -1
                      • B
                        BuZz administrators @shavecat
                        last edited by 9 Jun 2020, 00:47

                        @shavecat you should know how the forum works by now. Replying saying same issue with no information is useless. There's even a solution above.

                        Start a new topic and provide something to work with.

                        To help us help you - please make sure you read the sticky topics before posting - https://retropie.org.uk/forum/topic/3/read-this-first

                        S 1 Reply Last reply 7 Sept 2020, 16:22 Reply Quote 1
                        • S
                          shavecat @BuZz
                          last edited by shavecat 9 Jul 2020, 17:55 7 Sept 2020, 16:22

                          @BuZz
                          Hey so i change the
                          #hdmi_group=1
                          #hdmi_mode=16
                          too
                          hdmi_group=1
                          hdmi_mode=16

                          But i still getting this error

                          1 Reply Last reply Reply Quote 0
                          • S
                            shavecat
                            last edited by 16 Sept 2020, 17:26

                            Hey all back ,
                            So im still having this isuue with no overclock at all ! .
                            Plz any help ?

                            1 Reply Last reply Reply Quote 0
                            • S
                              shavecat @roslof
                              last edited by 2 Oct 2020, 12:43

                              @roslof
                              Did u get it fix at the end ?
                              having this issue for a month now... with no luck :\

                              R 1 Reply Last reply 2 Oct 2020, 13:03 Reply Quote 0
                              • R
                                roslof @shavecat
                                last edited by 2 Oct 2020, 13:03

                                @shavecat said in DRM_IOCTL_MODE_CREATE_DUMB failed: Cannot allocate memory:

                                @roslof
                                Did u get it fix at the end ?
                                having this issue for a month now... with no luck :\

                                I'm stable. Can't say I know for certain what change fixed the DRM message (assuming that's your issue) but no issues here at this time. All my relevant, personal changes are documented in this thread, except now I'm using a lighter theme and exclusively using the latest version of VLC, which renders screensaver video and ES videos when hardware acceleration is off.

                                Backup your data first, then I suggest reading through the thread and carefully experiment, reverting changes that you find don't help. Maybe try the Carbon theme (tried and true) for a bit and see how that goes. Be sure your software is up to date (mine is) as of last weekend.

                                S 1 Reply Last reply 2 Oct 2020, 13:07 Reply Quote 1
                                • S
                                  shavecat @roslof
                                  last edited by shavecat 10 Feb 2020, 15:45 2 Oct 2020, 13:07

                                  @roslof
                                  thanks a lot !
                                  yes its the same issue driving my nuts i really tried everything...
                                  will give it a try for all that u write here again :)
                                  hope for good and will say if worked .
                                  thank again

                                  1 Reply Last reply Reply Quote 0
                                  • S
                                    shavecat
                                    last edited by shavecat 10 Apr 2020, 15:42 2 Oct 2020, 23:44

                                    OKAY
                                    so nothing really helps :\
                                    Tried different themes switch off or on the omx player and all that :\

                                    DRM_IOCTL_MODE_CREATE_DUMB failed: Cannot allocate memory
                                    Failed to create scanout resource
                                    DRM_IOCTL_MODE_CREATE_DUMB failed: Cannot allocate memory
                                    Failed to create scanout resource
                                    
                                    

                                    Its just showing that after launch a game non stop on the left top screen crashing all.... :(((

                                    1 Reply Last reply Reply Quote 0
                                    • S
                                      shavecat
                                      last edited by shavecat 18 Oct 2020, 18:32

                                      So the issue was gone for like 2 weeks (but i didnt really play a lot with the pi )
                                      and it come back...
                                      i try everything
                                      uninstall and install back all emuatlinstaion .
                                      but nothing really helps
                                      its just pop on my left side on my screen after playing a few games and quit them .
                                      non stop untill it crush it self :(

                                      DRM_IOCTL_MODE_CREATE_DUMB failed: Cannot allocate memory
                                      Failed to create scanout resource
                                      

                                      im guessing no asnwer for that ... :((

                                      1 Reply Last reply Reply Quote 0
                                      • S
                                        shavecat
                                        last edited by shavecat 20 Oct 2020, 16:21

                                        So after delete the es_settings.cfg
                                        its stable for now...
                                        dont know what caused it really , and hope it will last for now :|)

                                        Guess not still crushing after quit some games :((

                                        1 Reply Last reply Reply Quote 0
                                        • G
                                          GreenHawk84 @roslof
                                          last edited by GreenHawk84 28 Dec 2020, 05:44

                                          Hello,

                                          I ended up getting this error after a long night of configuring bezels and such. Took about 3 hours to appear. I guess delete es_settings? Any adverse effects I should consider? I am on a Pi4 with stock settings.

                                          error.jpg

                                          S 1 Reply Last reply 28 Dec 2020, 10:51 Reply Quote 0
                                          • First post
                                            Last post

                                          Contributions to the project are always appreciated, so if you would like to support us with a donation you can do so here.

                                          Hosting provided by Mythic-Beasts. See the Hosting Information page for more information.

                                            [[user:consent.lead]]
                                            [[user:consent.not_received]]