devdocs icon indicating copy to clipboard operation
devdocs copied to clipboard

Bug: Lag / Stack Overflow on Phoenix Search Result

Open skyqrose opened this issue 4 years ago • 3 comments

Describe the bug Stack overflow on long search result.

To Reproduce Steps to reproduce the behavior:

  1. Add Phoenix as a source.
  2. Search for testing-librar (problem occurs when typing the second r)

Result:

Page lags for a while, then an error shows in the console. I can continue to interact with the page, but every action takes several seconds, until I delete the search term and the page becomes responsive again.

It freezes every time I search with testing-librar but does not reliably freeze when finding the same search result by searching for other terms.

Expected behavior No lagging, text in search results is trimmed. A clear and concise description of what you expected to happen.

Screenshots Screen Shot 2022-01-10 at 11 35 35

Desktop (please complete the following information):

  • OS: macOS Big Sur
  • Browser: Firefox 95.0.1

Additional context I recently started trying DevDocs for the first time. I added a few sources, and tried searching for a few terms, but it's otherwise a fresh state.

skyqrose avatar Jan 10 '22 16:01 skyqrose

Related issues wrt. "too much recursion": https://github.com/freeCodeCamp/devdocs/issues/1539, https://github.com/freeCodeCamp/devdocs/issues/1556, https://github.com/freeCodeCamp/devdocs/issues/1662

simon04 avatar Jan 10 '22 19:01 simon04

I am seeing this issue on firefox 118.0.2. Search term is Rust Hash and it just locks up for a while. Tried resetting my data (so there is nothing "downloaded") and I am still seeing the issue

Note: If I set the language to rust first (typing Rust and hitting Tab), I can search for rust things with no issue. So likely not related to rust doc specifically

miversen33 avatar Oct 19 '23 02:10 miversen33

Anecdotally (from when I reported #1539): this seemed to be an issue with searches that have either spaces or hyphens in them, and the freeze-up seemed to be correlated with when the space or hyphen character was reached in the input (ex: the space in "OpenJDK 11").

lorentzforces avatar Apr 08 '24 17:04 lorentzforces