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

Time travel seems broken #265

Closed
aspiers opened this issue Dec 11, 2021 · 1 comment
Closed

Time travel seems broken #265

aspiers opened this issue Dec 11, 2021 · 1 comment

Comments

@aspiers
Copy link

aspiers commented Dec 11, 2021

If I try to go back in time, the web page in questions goes blank (white) and I get errors like this:

Warning: Can't perform a React state update on an unmounted component. This is a no-op, but it indicates a memory leak in your application. To fix, cancel all subscriptions and asynchronous tasks in the componentWillUnmount method.
    at TransitionGroup (webpack://@my/app/../node_modules/react-transition-group/esm/TransitionGroup.js?:53:30)
    at span
    at eval (webpack://@my/app/../node_modules/@emotion/react/dist/emotion-element-1c22787f.browser.esm.js?:54:66)
    at TouchRipple (webpack://@my/app/../node_modules/@mui/material/ButtonBase/TouchRipple.js?:154:83)
    at button
    at eval (webpack://@my/app/../node_modules/@emotion/react/dist/emotion-element-1c22787f.browser.esm.js?:54:66)
    at ButtonBase (webpack://@my/app/../node_modules/@mui/material/ButtonBase/ButtonBase.js?:111:82)
    at eval (webpack://@my/app/../node_modules/@emotion/react/dist/emotion-element-1c22787f.browser.esm.js?:54:66)
    at Button (webpack://@my/app/../node_modules/@mui/material/Button/Button.js?:233:83)
    at div
    at div
    at div
    at div
    at CheckRegistration (webpack://@my/app/./src/components/CheckRegistration/index.tsx?:21:27)
    at div

It comes from timeJump.ts:16, which corresponds to the breakpointed line in this source fragment:

image

@garrettlchow
Copy link
Contributor

Good news! This white screen issue has been resolved in Reactime 26.0 with improvements to state restoration and time-travel debugging reliability.

To get the fix, simply update to the latest version of Reactime from the Chrome Web Store. If you continue to experience any issues after updating, please feel free to reopen this issue with details about your setup.

Thanks for helping us improve Reactime!

Closing as resolved

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