Skip to content
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

Kodi crash when game crash #18

Open
1 of 7 tasks
Canuma opened this issue Nov 14, 2018 · 2 comments
Open
1 of 7 tasks

Kodi crash when game crash #18

Canuma opened this issue Nov 14, 2018 · 2 comments

Comments

@Canuma
Copy link

Canuma commented Nov 14, 2018

Bug report

Describe the bug

Whenever a game crashes (into builtin debugger), Kodi crashes/ends too

RetroArch Behavior

Here is a clear and concise description of what happens in RetroArch with the same core/game:
Unknown, not installed

To Reproduce

Steps to reproduce the behavior:

  1. Launch ScummVM
  2. Import a known broken game/wrongly detected game
  3. Start Game
  4. Continue if debugger comes up

Debuglog

The debuglog can be found here:
No Debuglog. Yet. Might provide one on private basis.

Screenshots

Here are some links or screenshots to help explain the problem:
Please have a look here
I described several findings, this one seems to be reproducable

Your Environment

Used Operating system:

  • Android
  • iOS
  • Linux
  • OSX
  • Raspberri-Pi
  • Windows
  • Windows UWP

Operating system version/name: Windows 7 64

Kodi version: 18 beta 5

note: Once the issue is made we require you to update it with new information or Kodi versions should that be required.
Team Kodi will consider your problem report however, we will not make any promises the problem will be solved.

@garbear
Copy link
Member

garbear commented Nov 17, 2018

Kodi crashes because the core is run in the same process space, and a segfault anywhere bring down Kodi too. The solution is to run all cores out-of-process, but this is difficult because we support so many platforms and each one has their own inter-process communication protocol (if one exists on the platform at all).

@Canuma
Copy link
Author

Canuma commented Nov 21, 2018

Oh, that's a real showstopper then at least for scumm vm i'm afraid. Because there always might be something going on and usually it then crashes to the debugger, as mentioned. Isn't there another way to trap that specific core, so that it could just stop working? (I have no idea about that stuff, I am just a little java coder, so i can't do much to help here)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants