3 ms·

oh hm, i thought I had fixed every case where that popped up. I can't reproduce the issue on any browser on my machine - how did you jump to the bottom (hotkey,

by eieio 2y ago

oh hm, i thought I had fixed every case where that popped up. I can't reproduce the issue on any browser on my machine - how did you jump to the bottom (hotkey, scrollbar, scrolling for a trillion years) and what platform are you on (if you don't mind sharing)?

LCoder 2y ago
Chome on Windows. Grab the right scroll bar and pull to the very bottom. Once at the bottom try to scroll down with mouse scroll wheel. Screen goes blank and the error appears in the console.
- eieio 2y ago
  OH! Thanks for the precise reproduction steps, I had done my testing with a trackpad and had missed that! Writing a little fix now (I'd hate for you to not be able to see the last UUID)
  - jonny_eh 2y ago
    > I'd hate for you to not be able to see the last UUID No spoilers, but the last one's a doozy!
    - efdee 2y ago
      Number #553752677 will surprise you!
      - saagarjha 2y ago
        It's actually number #5316911983139663491615228241121378304 if you were keeping count.
- blahyawnblah 2y ago
  Same for me on Firefox windows
- eieio 2y ago
  alright, a fix that I think covers this crash and a few others I found as a result is rolling out now. for a while I thought I had an off by one error, which was pretty funny to think about in the context of trillions of items. but in fact I was just doing some bad react state management.
  - rel_ic 2y ago
    fixed for me! Brave MacOS
gabeio 2y ago
use the scroll bar to get to the "end" then use scroll wheel. that's how I managed to hit it reliably.