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

Debouncer in session recording causes frames to be skipped #130

Closed
RCVZ opened this issue Dec 12, 2024 · 1 comment · Fixed by #131
Closed

Debouncer in session recording causes frames to be skipped #130

RCVZ opened this issue Dec 12, 2024 · 1 comment · Fixed by #131
Labels
bug Something isn't working

Comments

@RCVZ
Copy link

RCVZ commented Dec 12, 2024

Version

4.7.1

Steps to Reproduce

  1. Enable session recording as described in the documentation.
  2. Set debouncerDelay to 1 second.
  3. Use the app quickly, performing a series of rapid interactions or actions.
  4. Review the recorded session.

Expected Result

The session recording should at least capture one frame of every screen/interaction, accurately reflecting user interactions without noticeable skips.

However, because a debounce is used it is expected that frames are skipped.
Decreasing the debounce time to 100ms is not an option this can cause too much overhead.

Actual Result

Frames of certain screens/interactions are skipped in the recorded session, resulting in an incomplete(sometimes useless) playback.

@RCVZ RCVZ added the bug Something isn't working label Dec 12, 2024
@marandaneto
Copy link
Member

Hey @RCVZ thanks for the feedback.
Here is the PR #131
We considered throttling before but thought it'd just cause performance issues, but if it's also recording useless recordings, this is no good, let's try a throttling approach.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants