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

    New bug/crash from 15 days with new ES release

    Scheduled Pinned Locked Moved Help and Support
    emulationstaioncrashbuginputmanagerretropie-setup
    53 Posts 10 Posters 15.2k 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.
    • darkniorD
      darknior
      last edited by

      @hex I do it every day, and try it now, it do nothing when i take the keyboard on. It works fine and the PI don't crash.

      My PowerSaver Modes was already Disabed ... i forgot this lol
      I put it default to try. i don't know what are doing extended and instant options.

      Life is game, just play it !

      pjftP 1 Reply Last reply Reply Quote 0
      • pjftP
        pjft @darknior
        last edited by

        @darknior sorry, I wasn't suggesting you to update it - it was more a question of had you updated it recently, and whether that update would be causing the problems.

        As I said, nothing really changed on the ES front that I'm aware of, though I can check tomorrow, so I'm not really sure why you'd only have started to observe this now.

        1 Reply Last reply Reply Quote 0
        • HexH
          Hex
          last edited by

          @pjft Considering that he has PS options I am guessing he is running >v2.5

          Sent from 20,000 leagues under the sea.

          Powersaver Emulation station : https://github.com/hex007/EmulationStation
          ES dev script : https://github.com/hex007/es-dev/blob/master/es-tests.sh

          pjftP 1 Reply Last reply Reply Quote 0
          • pjftP
            pjft @Hex
            last edited by

            @hex I was referring to the Bluetooth drivers or OS, as I don't think anything changed in ES's InputManager, but maybe I'm mistaken.

            1 Reply Last reply Reply Quote 0
            • darkniorD
              darknior
              last edited by

              @pjft From yesterday i activate the Power Saver option to default, my PI not crashing again.
              I'll let it work like that several days to see ...

              Life is game, just play it !

              1 Reply Last reply Reply Quote 0
              • HexH
                Hex
                last edited by

                @pjft This is the first time that PS enabled solved a problem :)

                @darknior The problem is present in ES. PS enabled (default) might just be hiding it due to the wake ups and sleeps. Try reproducing it using PS disabled. If you are able to reproduce it consistently then we have a bug.

                Sent from 20,000 leagues under the sea.

                Powersaver Emulation station : https://github.com/hex007/EmulationStation
                ES dev script : https://github.com/hex007/es-dev/blob/master/es-tests.sh

                1 Reply Last reply Reply Quote 0
                • T
                  ttusoulfan
                  last edited by

                  so i have been having a similar issue,except that when i go to install the roms it gives the a similar error.

                  1 Reply Last reply Reply Quote 0
                  • darkniorD
                    darknior
                    last edited by

                    Ok @Hex . Tonight i let it with the option enable, and if it not crash, tomorrow i will disabling it again.
                    But how to help you to repair it ? Can i have some logs ?

                    Life is game, just play it !

                    1 Reply Last reply Reply Quote 0
                    • HexH
                      Hex
                      last edited by

                      Do not connect any bluetooth devices while testing. I will not need logs as the error is an assert failing. So I can study it based on if it fails due to PS.

                      Can you tell me if you have screensaver enabled? and of what type?

                      Sent from 20,000 leagues under the sea.

                      Powersaver Emulation station : https://github.com/hex007/EmulationStation
                      ES dev script : https://github.com/hex007/es-dev/blob/master/es-tests.sh

                      darkniorD 1 Reply Last reply Reply Quote 0
                      • C
                        ChauncyBlack
                        last edited by

                        I can confirm this freezing during idle is caused by a recent emulation station update. I'm running on a combination of RPi3, Retropie 4.2, a known good SD card, and 2 Logitech wireless Rumblepad 2 joysticks. The system had been running flawlessly until my most recent updates of installed base packages (via apt-get update/upgrade), kernel (via rpi-update, currently at 4.9.45), and Retropie packages (via retropie_setup.sh), about a week ago (around August 20 or so). Previous full system update took place around end of June or beginning of July, and had been running fine. Once this freezing behavior started, I thought maybe the update process had corrupted the file system (as it has happened to me before), so I did a completely clean install using the 7/5/17 raspian lite image (last official Jesse release) and a manual install of the retropie script (git clone, etc.). The problem immediately reappeared.

                        I am using a wired network connection; wifi is on but unused. Bluetooth is on, but no devices are connected. If left idle after booting into emulation station, the system will soft-hang in about an hour, with video and joysticks becoming unresponsive. If I attempt to log in via ssh, the terminal appears to hang, but I can Ctrl-C out of the hung logon process and get a prompt. A dmesg query returns a number of repeated warning about a hung kworker thread being unresponsive for over 120 seconds. That repeats in the log 4 or 5 times, and then the log ends. The process id of the hung kworker thread changes every time. A query with "journalctl -p 3 -xb" gives similar error messages. I haven't been able to find anything else in the logs. At this point in the process, if I attempt a "sudo reboot", my terminal session terminates, but the RPi never actually reboots.

                        I have found that if I restart the system and quit out of emulation station to the command line, the system remains responsive and functions as expected (e.g. I can login via terminal normally, I can reboot, and dmesg and journalctl behave and expected) and has done so for about six hours since my last reboot.

                        Hope that helps.

                        1 Reply Last reply Reply Quote 0
                        • pjftP
                          pjft
                          last edited by

                          The file in question hasn't been changed since April, and it has been only for minor maintenance issues. :/

                          Unless it'd be related to something with Power Savings (which I'm not clear that it would, given the reports from @darknior ), we might be on the wrong track here.

                          @ChauncyBlack does this also happen if you disable Power Savings?

                          1 Reply Last reply Reply Quote 0
                          • SanoS
                            Sano
                            last edited by

                            FYI , someone had similar errors 7 months ago (no PS at the time) :
                            https://retropie.org.uk/forum/topic/7744/repeatable-crash-w-bluetooth-error

                            Could it be related to SDL ?

                            pjftP 1 Reply Last reply Reply Quote 1
                            • pjftP
                              pjft @Sano
                              last edited by

                              @sano My bet is that it is indeed related to ES input management via SDL or the underlying OS drivers, and has been there for a while now. But without hard evidence it's hard to narrow down what may be affecting this.

                              1 Reply Last reply Reply Quote 0
                              • SanoS
                                Sano
                                last edited by Sano

                                According to @bmn001 post, it was only happening when he powered off his controllers after exiting a game, but before full ES reload.

                                Just a guess, could be totally wrong but that seems logical :
                                Without knowing the code, we could assume that the function crashing (AddJostckByDeviceIndex ?) has problem if a BT device disappears right before the call.
                                If it's right, that could at least tend to prove that 7 months ago this function only was called during ES launch, and is now called on a more regular basis.

                                Edit : of course this won't narrow the bug reasons, but would prove it was already existing, and explain why it seems to happen more frequently...

                                1 Reply Last reply Reply Quote 0
                                • pjftP
                                  pjft
                                  last edited by

                                  This is only called in Window::init(), specifically in InputManager::getInstance()->init();.

                                  This function is called at launch, and every time returning from a game back into ES (where we re-initialize the Window object).

                                  The code is:

                                  int numJoysticks = SDL_NumJoysticks();
                                  for(int i = 0; i < numJoysticks; i++)
                                  {
                                  	addJoystickByDeviceIndex(i);
                                  }
                                  

                                  and then the assertion is

                                  assert(id >= 0 && id < SDL_NumJoysticks());
                                  

                                  So, reading the code:

                                  • id is always >= 0 (it is the iin the cycle)
                                  • so this must be failing because, at some point, id is >= to the SDL_NumJoysticks() returned.

                                  Now, this is an awful thing to test or review, as the cycle by definition on runs for i = 0to i < SDL_NumJoysticks() so it means that sometime during the cycle the number of joysticks being returned by SDL is being reduced.

                                  An extra layer of logging there would certainly help troubleshoot this.

                                  Also, if one of you experiencing this could SSH into the Pi after it crashes and retrieve the content of ~/.emulationstation/es_log.txt (or, actually, after restarting, ~/.emulationstation/es_log.txt.bak should be the backup of the previous session if you're on 2.6.0) it may be helpful.

                                  1 Reply Last reply Reply Quote 1
                                  • HexH
                                    Hex
                                    last edited by

                                    @pjft I think this is a one time thing. The bluetooth controller must have disconnected at the exact time when it was processing this loop and caused a crash. If @darknior can reproduce this even once then we might be able to bisect it.

                                    Sent from 20,000 leagues under the sea.

                                    Powersaver Emulation station : https://github.com/hex007/EmulationStation
                                    ES dev script : https://github.com/hex007/es-dev/blob/master/es-tests.sh

                                    pjftP 1 Reply Last reply Reply Quote 0
                                    • pjftP
                                      pjft @Hex
                                      last edited by

                                      @hex my suggestion is that this is not really new, though, but certainly keen on hearing more about it.

                                      1 Reply Last reply Reply Quote 0
                                      • HexH
                                        Hex
                                        last edited by

                                        ES mostly runs on a single thread and this entire process runs sequentially. So PS actually doesnt interrupt this

                                        Sent from 20,000 leagues under the sea.

                                        Powersaver Emulation station : https://github.com/hex007/EmulationStation
                                        ES dev script : https://github.com/hex007/es-dev/blob/master/es-tests.sh

                                        1 Reply Last reply Reply Quote 0
                                        • C
                                          ChauncyBlack
                                          last edited by

                                          @pjft Power savings doesn't seem to have an effect either way. The hang state repeats regardless.

                                          In response to sano's suspicion that it may be SDL related, I do recall seeing some sort of SDL-related error when installing the retropie setup script. From the install logs:

                                          dpkg: dependency problems prevent configuration of libsdl2-2.0-0:armhf:
                                          libsdl2-2.0-0:armhf depends on libxcursor1 (>> 1.1.2); however:
                                          Package libxcursor1 is not installed.
                                          libsdl2-2.0-0:armhf depends on libxi6 (>= 2:1.2.99.4); however:
                                          Package libxi6 is not installed.
                                          libsdl2-2.0-0:armhf depends on libxinerama1; however:
                                          Package libxinerama1 is not installed.
                                          libsdl2-2.0-0:armhf depends on libxrandr2 (>= 2:1.2.99.3); however:
                                          Package libxrandr2 is not installed.
                                          libsdl2-2.0-0:armhf depends on libxss1; however:
                                          Package libxss1 is not installed.
                                          libsdl2-2.0-0:armhf depends on libxxf86vm1; however:
                                          Package libxxf86vm1 is not installed.

                                          dpkg: error processing package libsdl2-2.0-0:armhf (--install):
                                          dependency problems - leaving unconfigured
                                          dpkg: dependency problems prevent configuration of libsdl2-dev:armhf:
                                          libsdl2-dev:armhf depends on libsdl2-2.0-0 (= 2.0.5+5rpi); however:
                                          Package libsdl2-2.0-0:armhf is not configured yet.
                                          libsdl2-dev:armhf depends on libgl1-mesa-dev; however:
                                          Package libgl1-mesa-dev is not installed.
                                          libsdl2-dev:armhf depends on libx11-dev; however:
                                          Package libx11-dev is not installed.

                                          dpkg: error processing package libsdl2-dev:armhf (--install):
                                          dependency problems - leaving unconfigured
                                          Processing triggers for libc-bin (2.19-18+deb8u10) ...
                                          Processing triggers for man-db (2.7.5-1~bpo8+1) ...
                                          Errors were encountered while processing:
                                          libsdl2-2.0-0:armhf
                                          libsdl2-dev:armhf

                                          Could these be at all related?

                                          1 Reply Last reply Reply Quote 0
                                          • HexH
                                            Hex
                                            last edited by

                                            @ChauncyBlack Your bugs are not related please open a new thread

                                            Sent from 20,000 leagues under the sea.

                                            Powersaver Emulation station : https://github.com/hex007/EmulationStation
                                            ES dev script : https://github.com/hex007/es-dev/blob/master/es-tests.sh

                                            1 Reply Last reply 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.