No, it doesn’t crash - at least not right away - if you repeat the process: “Load Core” - “Load Content” - “Close Content” - since the core isn’t unloaded or closed until the BIOS has fully loaded - “Load Content” (another game) - “Close Content” - repeat 3 times; after that, the entire RetroArch crashes (this may be specific to my hardware; you can try repeating this experiment. I’m considering it solely from a testing perspective, not as a real-world usage scenario).
Yeah, and it works great! Thanks for this feature - I love sometimes listening to tracks from the game on CD-player 
The “Unload Core” button is only available if the core is not running; if the core is already running and has loaded into the BIOS, the “Unload Core” button is not displayed.
As I mentioned earlier, I sometimes download new game images and run them to test their functionality. After that, I usually rename the image according to my naming convention (title, region, game serial number, language, country of release), find the corresponding box art, and then add the game to my PlayStation playlist and link the appropriate core to it. But sometimes I don’t have time to neatly organize a new game in the playlist, so I just settle for a quick check to see if the image works. In those cases, I use this scenario: “Load Core” - “Load Content” - wait for all the opening intros to play, start the game until the character appears - “Close Content.” In this scenario, the Beetle PSX HW and SwanStation cores close the content but do not unload the core or boot the BIOS, unlike GooseStation. Sometimes I want to test a game with a different core (by default, all games from my PlayStation playlist open using the Beetle PSX HW core); in such cases, I also prefer to use the scenario “Load Core” - “Load Content” - to check the aspects of the game that interest me using the current core settings - “Close Content,” rather than reassigning the core in the playlist, and then reverting to the default core after testing and experimentation.
During my experiments, I tested a scenario where, conversely, we first select “Load Content” and then choose a core for that content - with this sequence of actions, closing the content while using the GooseStation core does not trigger a subsequent boot into the BIOS, and both the content and the core are completely unloaded. I guess I just need to get used to this specific sequence of actions 


