-
Notifications
You must be signed in to change notification settings - Fork 3
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
[Guider] Development builds sometimes throw runtime errors when using search #55
Labels
Comments
I triggered it again and copied the full stack trace
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Could not replicate in a production build.
When running a development build of Guider and search is used, a React runtime error will sometimes be thrown. This seems to be tied to the resource usage of the system, likely triggering some sort of race condition.
This was seen specifically when trying to use the Peek application on Ubuntu to record a gif of the search feature. It should also be noted that the project in question has around 500 pages in it, which may contribute to the load issue.
Killing some processes locally to free resources seems to have fixed this, which means it's likely tied to resource usage.
I understand this is hard to replicate and thus diagnose, so not expecting a fix anytime soon. Specific specs to try and replicate (taken straight from neofetch):
Which package/app is affected (leave empty if unsure)
@neato/guider
Link to the code that reproduces this issue
No response
Steps to reproduce
Try to use search in a project with lots of pages under heavy load. Specifics are unknown
Expected Behavior
To not have this error
Extra details
Gif of the error happening live
The text was updated successfully, but these errors were encountered: