You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have searched the issue tracker for a bug report that matches the one I want to file, without success.
What package is this bug report for?
rrweb
Version
2.0.0-alpha.5
Expected Behavior
I am able to seek without chrome tab crashing
Actual Behavior
Using the latest alpha version, with useVirtualDom: true, when I scrub around (drag progress bar or click seek forward or backward repeatedly, which calls player.play(time)) my chrome tab crashes with error code 5.
If I set useVirtualDom: false and scrub the tab does not crash.
Additionally, if I bump down to 2.0.0-alpha.4 I am not able to reproduce the bug with or without virtual DOM enabled.
This happens for every recording I play in my player, so I have not included a test set of events.
Additionally, I'm not really great at debugging these sort of issues, but I did run the chrome profiler, and it looks like it could be some sort of memory leak?
Let me know if I can provide any additional information to help debug. Thanks!
Steps to Reproduce
See above
Testcase Gist URL
No response
Additional Information
No response
The text was updated successfully, but these errors were encountered:
Preflight Checklist
What package is this bug report for?
rrweb
Version
2.0.0-alpha.5
Expected Behavior
I am able to seek without chrome tab crashing
Actual Behavior
Using the latest alpha version, with
useVirtualDom: true
, when I scrub around (drag progress bar or click seek forward or backward repeatedly, which callsplayer.play(time)
) my chrome tab crashes with error code 5.If I set
useVirtualDom: false
and scrub the tab does not crash.Additionally, if I bump down to
2.0.0-alpha.4
I am not able to reproduce the bug with or without virtual DOM enabled.This happens for every recording I play in my player, so I have not included a test set of events.
Additionally, I'm not really great at debugging these sort of issues, but I did run the chrome profiler, and it looks like it could be some sort of memory leak?
Let me know if I can provide any additional information to help debug. Thanks!
Steps to Reproduce
See above
Testcase Gist URL
No response
Additional Information
No response
The text was updated successfully, but these errors were encountered: