`retro_frame_time_callback_t` does not act like document
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
Start with the callback contract in include/libretro.h at the linked line and compare it with the observed call sequence around the first retro_run(). Trace the initial frame lifecycle to identify where the documented timing diverges. Done means the implementation and documentation agree about when retro_frame_time_callback_t is called and the reported deadlock scenario is resolved.
Written by the indexing model from the issue text.
Description
I'm writing a core with libretro and get a deadlock following the document/header file. After doing some trace I found retro_frame_time_callback_t is not called before first retro_run().
It will be called right before retro_run() every frame.
- Dominant language
- C
- Stars
- 180
- Forks
- 99
- Avg merge
- 7h 16m
- Merged PRs (30d)
- 1
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from libretro/libretro-common
-
linked_list remove-matching functions crash on a NULL callbackPossibly taken @Awesome-00 claimed this 12 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
libretro/libretro-common#232 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
libretro/libretro-common#220 · 1 comment · 1 reaction ·
-
RETRO_ENVIRONMENT_ clash in libretro.hPossibly taken @Clownacy claimed this 28 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
libretro/libretro-common#89 · 2 comments ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
libretro/libretro-common#223 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 38/100
libretro/libretro-common#221 · 1 reaction ·
All issues in libretro/libretro-common
Similar issues
-
IO.get_env on Node truncates names at embedded NULPossibly taken @Yi-111-a claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
HigherOrderCO/Bend#1449 · 1 comment ·
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
FujiNetWIFI/fujinet-firmware#1872 ·
Maintainers usually reply within 1 day
-
bug C/C++ code
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
webarkit/WebARKitLib#84 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
OpenPrinting/cups#1751 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
obsproject/obs-studio#14013 ·
Maintainers usually reply within 1 day