Emulator Issues #6529
closed
FifoPlayer requires dual-core to be disabled to avoid overflow/crash
Added by pauldacheez over 11 years ago.
Updated over 8 years ago.
Relates to performance:
No
Relates to maintainability:
No
Description
Three solutions for this:
- Fix it properly and make the CPU thread not overflow the FIFO GatherPipe in dual-core (or whatever it's doing). Difficult and pointless.
- Disable dual-core if a FIFO log's being played. Easy and probably the best choice.
- Swap out Dolphin's built-in FifoPlayer for Neobrain's homebrew one which may or may not still have this issue. Will likely happen at some point, which may be enough justification for everyone to ignore this.
(Normally this wouldn't be worth filing an issue about, but I've needed some issue-writing practice, so why not!)
- Status changed from New to Accepted
I like this issue a lot.
I'm going with accepted rather than won't fix because solution 2 sounds like it's be menial to do. Maybe this needs an easy tag.
If someone wants to override me and say wontfix, so be it, but I have a feeling one of the solutions from 2 or 3 will be used anyway regardless.
- Milestone set to Next
- Operating system N/A added
Nope, this definitely needs to be fixed. I'd avoid 2 since it's just a band-aid fix and this is not critical.
- Milestone changed from Next to Current
4.0 was released, moving Milestone-Next to Milestone-Current.
I guess this is the proper issue (or at least related to the problem).
I had an error popup "FIFO is overflowed by GatherPipe ! CPU thread is too fast !" in two games.
-No More Heroes (RNHE41), during the initial cutscene when raiding the mansion.
-Hitman 2 (GHMP4F), on the second level with the falling snow (ex-CR1 bug area).
We can go on by clicking the Yes button (No closes Dolphin), but there are tens of them each time.
Disabling the Panic handlers makes the screen freeze instead.
- Milestone changed from Current to Next
Moving to next milestone since these issues are not critical to a new release.
If you feel strongly about this issue and want it to block the next Dolphin release, please assign yourself as owner and re-add Milestone-Current.
Issue 8058 has been merged into this issue.
- Milestone changed from Next to Current
5.0 was released, moving Milestone-Next to Milestone-Current.
- Status changed from Accepted to Fixed
Nope, this was fixed some months ago.
#3573
4.0-8828-gea3a457
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by 
Updated by 
Updated by