RetroPie forum home
    • Recent
    • Tags
    • Popular
    • Home
    • Docs
    • Register
    • Login
    1. Home
    2. Tags
    3. segmentation
    Log in to post
    • All categories
    • M

      Redream crashes with segmentation fault when trying to access redream menu in game

      Watching Ignoring Scheduled Pinned Locked Moved Help and Support redream segmentation redream menu crash
      4
      0 Votes
      4 Posts
      386 Views
      M

      @sugarfree FIXED IT
      Turns out uninstalling redream does not clear the config files. manually going to opt/retropie/configs/dreamcast and clearing everything then removing and reinstalling redream though retropie setup has seemingly fixed it. redream menu now opens in game.

    • M

      Segmentation Faults in runcommand.sh when running N64 Games

      Watching Ignoring Scheduled Pinned Locked Moved Help and Support segmentation n64 crash
      14
      0 Votes
      14 Posts
      2k Views
      M

      I was able to convert my .srm save file from lr-mupen64plus-next to an .sra file with this online tool.

      https://drehren.github.io/ramp64-convert-web/

      I then copied the .sra file into /opt/retropie/configs/n64/mupen64plus/save/

      Then I launched ocarina of time with mupen64plus-GLideN64 and played it nonstop for about 2 hours without any crashes or major issues. GLideN64 may have had a few more video glitches than lr-mupen64plus-next was having, but not a single crash for that entire period of time, and that was picking up the game where I left off playing with lr-mupen64plus-next.

      So it seems that I don't have these crashes with standalone emulators, but do with libretro emulators.

    • M

      lr-dolphin segmentation fault

      Watching Ignoring Scheduled Pinned Locked Moved Help and Support lr-dolphin segmentation fault
      3
      0 Votes
      3 Posts
      387 Views
      mituM

      @mozvillat Please add some info about your setup, as detailed in https://retropie.org.uk/forum/topic/3/read-this-first.

      Get a verbose log from the error run and post it on pastebin.com.

    • B

      PS1 Game stopped working randomly

      Watching Ignoring Scheduled Pinned Locked Moved Help and Support segmentation psx
      1
      0 Votes
      1 Posts
      253 Views
      No one has replied
    • S

      Intellivision lr-freeintv Segmentation fault

      Watching Ignoring Scheduled Pinned Locked Moved Help and Support lr-freeintv intellivision segmentation
      17
      0 Votes
      17 Posts
      1k Views
      R

      It's working for me now as well, thank you.

    • R

      RetroPie error on Pi 3

      Watching Ignoring Scheduled Pinned Locked Moved Help and Support errors segmentation help with retro
      2
      0 Votes
      2 Posts
      347 Views
      mituM

      Please add some info about your setup and issue, as detailed in https://retropie.org.uk/forum/topic/3/read-this-first.

      Are you using the RetroPie Pi3 image from retropie.org.uk/download ?

    • X

      Segmentation fault when playing specific games

      Watching Ignoring Scheduled Pinned Locked Moved Help and Support mame2000 segmentation
      3
      0 Votes
      3 Posts
      1k Views
      X

      @buzz Thanks for your response.

      I might be that. I used that specific version of mame because I already had some roms from the appropiate romset.

    • P

      Kodi Segmentation Fault error

      Watching Ignoring Scheduled Pinned Locked Moved Help and Support kodi segmentation fault
      25
      0 Votes
      25 Posts
      4k Views
      D

      @Rascas the issue is max_framebuffers=2 on retropie. It should be max_framebuffers=1 when using a single display. This resolved my issue.
      Tried all different cables, monitor inputs, monitor outputs, rebuilding libcec. only solution was max_framebuffers=1.

      Thread here shows it should be set to match your displays. https://www.raspberrypi.org/forums/viewtopic.php?t=245789

      I'll accept maybe it's an oddity with my display, but since making that change i've been unable to reproduce it.

      Think the corruption was perhaps bad luck... but I've seen a few reports of recent kernel/raspbian updates causing this.

    • A

      Segmentation fault on lr-ppsspp

      Watching Ignoring Scheduled Pinned Locked Moved Help and Support lr-ppsspp segmentation fault
      2
      0 Votes
      2 Posts
      338 Views
      J

      @akamming I confirm the same problem and the same error. It seems to be related to some parameter in the config files (maybe retroarch or core options).

    • R

      RetroArch Segmentation Fault on launch

      Watching Ignoring Scheduled Pinned Locked Moved Help and Support retroarch segmentation fault odroid xu4
      2
      0 Votes
      2 Posts
      1k Views
      BuZzB

      I've not tested on my odroid xu for some weeks. May be a recent change broke something. I'll check when I next get a chance.

      May be a retroarch issue.. you could try rolling back the RetroPie-Setup script and building the previous version. I don't have time now however to give instructions to do this sorry.

    • S

      Segmentation fault mupen64plus-next

      Watching Ignoring Scheduled Pinned Locked Moved Help and Support mupen64plus-nex segmentation
      4
      0 Votes
      4 Posts
      533 Views
      S

      raspberry 3b+ , retroarch 1.8.4 , retropie 4.5.1. Touch wait for the solution.

    • MortisantiM

      Some PlayStation Games Failing to Fully Launch

      Watching Ignoring Scheduled Pinned Locked Moved Help and Support psx playstation segfault segmentation blackscreen
      3
      0 Votes
      3 Posts
      871 Views
      MortisantiM

      @mitu Glad to know I'm not the only one having the issue with Arcade's Greatest Hits - The Atari Collection 1. The fact that both of these games play properly on ePSXe, using the same BIOS (SCPH1001.bin) and ROM files, leads me to believe that it's an issue with lr-pcsx-rearmed. I suppose, worst case scenario, I could try The Atari Collection 1 on SNES and Hot Wheels Turbo Racing on N64 if myself or anyone else can't figure out the issue on PSX.

      Related links: Hot Wheels Turbo Racing psx black screen
      PS1 games that have bugs in retropie

    • T

      Segmentation fault when switching on video previews

      Watching Ignoring Scheduled Pinned Locked Moved Help and Support video preview segmentation fault
      1
      0 Votes
      1 Posts
      392 Views
      No one has replied
    • E

      Error "corrupted double-linked list" & "Segmentation Fault"

      Watching Ignoring Scheduled Pinned Locked Moved Help and Support corrupted double-linked segmentation fault
      12
      0 Votes
      12 Posts
      2k Views
      E

      H264 runs perfectly. Thanks!

    • BobHarrisB

      Segmentation fault while creating custom collection

      Watching Ignoring Scheduled Pinned Locked Moved Help and Support segfault segmentation fault game collection
      1
      0 Votes
      1 Posts
      518 Views
      No one has replied
    • S

      Segmentation faults with mupen64plus after update

      Watching Ignoring Scheduled Pinned Locked Moved Help and Support segmentation nintendo 64 mupen64plus runcommand
      16
      2 Votes
      16 Posts
      6k Views
      A

      @jonnykesh At first I updated the standalone mupen64plus package from source but it didn't solve the problem so I updated the lr-mupen64plus package too.

      In reddit someone wrote that it should work from now on with an update from the binarys.
      I tried the mupen64plus update from binarys and now it works :D

    • C

      Pi3B, MAME, lr-MameForAll or lr-Mame03 - Segmentation Faults

      Watching Ignoring Scheduled Pinned Locked Moved Help and Support segmentation raspberry pi 3b lr-mame2003 lr-mame4all
      18
      0 Votes
      18 Posts
      6k Views
      RiverstormR

      @darksavior said in Pi3B, MAME, lr-MameForAll or lr-Mame03 - Segmentation Faults:

      Games will have bugs or not run correctly. You might not have noticed it, but I did. It depends on the game.

      I agree with that between 0.36 and 0.78 it nearly doubled and between lr-mame2000 and lr-mame2003 I would think a shoe in for the latter and is considered the gold standard in certain aspects except maybe vector where AdvMAME outshines them all. I do agree to that FBA seems to run Neo-Geo, Capcom, Konami games better. They just seem to run smoother for certain.

      I do also use multiple emulators too depending on the game. Mainly lr-mame2003 roughly 300 or so games with aforementioned options of shader and analog d-pad support. AdvMAME for vector, FBA for Neo-Geo, etc.

      The original author of mame4all-pi (squid) had a majority of the games running at 100% without frame skip. It's been a hobby of mine since the late 90's. I do faithfully download the split updates every few months merge it and join the torrent. That includes the CHD's & extras, etc. I think it's close to 400GB now. It's where I spend most of my time when it comes to emulation.

      That's what I was pointing out is the binaries (ROMs) are mostly 100% identical between the two version which are only 3 years apart. I don't believe the driver/board support emulation improved that much between those versions but they went crazy with additions.

      You would have to be more specific on what exact games you find buggy in 0.37b5 that work differently in 0.78? My main point is that mame4all-pi (not lr-mame2000) is still very relevant if not a choice not just for the familiarity and support for being so widely ported but also the input configuration is still superior out of the box it works. Meaning there's certain configuration scenarios lr-mame2003 can't do...yet or at least not easily as I believe you will loose hotkey functionality if you "nul" all the Retroarch inputs to rely on lr-mame2003 inputs alone to correct the issue. :)

    • F

      Sega Mysteriously Stopped Working (error log within)

      Watching Ignoring Scheduled Pinned Locked Moved Help and Support sega segmentation reinstall
      7
      0 Votes
      7 Posts
      2k Views
      mediamogulM

      @FrustratedUser

      Glad to hear it.

    • J

      Segmentation Fault Screen

      Watching Ignoring Scheduled Pinned Locked Moved Help and Support segmentation
      20
      0 Votes
      20 Posts
      13k Views
      Z

      @martincrocenzi said in Segmentation Fault Screen:

      @zoop did you reboot the raspberry? when exactly do you get that screen? Can you detail the text or message you receive? Any capture or pic? Which Raspberry do you have? Which sd card? Any other specs? Whta do you mean with too aggressive?

      Thanks!

      I used a kit I ordered from Amazon for my PI setup. The details may be found here, including the details on the SD card: https://www.amazon.com/gp/product/B01LWURJMI/ref=oh_aui_detailpage_o01_s00?ie=UTF8&psc=1

      Pi Model or other hardware: PI 3 Model B
      Power Supply used: 5V/2.5A Power supply charger for Raspberry 3B
      RetroPie Version Used (3.6, 3.8.1, 4.01 etc.. - do not write latest): 4.1
      Built From: Pre made SD Image on RetroPie website

      The overclock settings I am using without issues are (credit YouTube vid where I found them):

      https://www.google.com/url?sa=t&source=web&rct=j&url=%23&ved=0ahUKEwjkiPON2a3SAhWD1CYKHQKjD00QwqsBCDUwAg&usg=AFQjCNF1sHlk2z9QIx28jtvfnGP_UlkifA&sig2=JVDtgTiyUALlhDTby_3i1A

      Stable settings for me:

      gpu_mem=400
      arm_freq=1400
      over_voltage=6
      sdram_freq=500
      core_freq=500
      gpu_freq=400

      When I bumped the arm_freq up to 1450 I received the aforementioned error. Resolving the issue on my end was as simple as modifying my config.txt to scale back the arm_freq to 1400 again and powering the system off then back on again. To my great relief everything just worked once the setting had been changed back to a stable configuration.

      I do not 100% remember how the screen looked with the error. It may have just been a single line reading segmentation fault. All I remember for sure is there was a 'segmentation fault error' on the screen and I figured it had to be my OC settings. I just had to hope I had not corrupted my image or something..

      Apologies for the delayed response, I hope you find what you're looking for and are able to resolve the issue. Best luck!