Update on the issue (and the solution)

It seems like a possible solution (at least to me) is to probably avoid having a generator tab open with so many comment frames at once, as they’re constantly filling up the whole TCP connection with requests for listening for new comments every time, which is what’s causing the “stalled” problem every time I load and save generators.

See this comment for a reference.

Update 1: Now I’ve just sort of reproduced this by opening the Comments Plugin tab while one of my generators is saving, and then after the tab is being open and then closed, the saving process just stalled out of nowhere.

Recently I was hit by the problem where the saving process just stuck in the background, and when I checked the DevTools Network, there’s a lot of stalled connections when fetching a few resources required for the generator page to fully load. The stall eventually ends for a short time (1-30 min), but sometimes even longer (30-60 minutes), and even after that, it’s either still hangs on “saving” whatsoever, or it rolls back to the perviously “unsaved” state.

I also got the problem with loading generators too, where it hangs very frequently now, for the same reason, except that I sometimes get an ERR_QUIC_PROTOCOL_ERROR from the console whenever the generator fails to load after the stalled connections.

Is this maybe just because of the internet connection, my browser, or probably the “cache-busting” issue in the end? I tried logging into my other browser (Firefox) and saving the same generator and found no issues. It also loads generators perfectly fine.

  • BluePowerOPEnglish
    1·
    6 months ago

    One thing I did noticed is that you still have lots of singular requests to the generatorStats API…

    Yeah, I know that and actually have been using it to calculate the total views thing, but the repetitive generatorStats requests isn’t necessarily a major problem anyways, but I think I’ll need to use that alternative technique to retrieve the generator stats for each of the generators there, I suspect that was a repetitive call of the generatorStats API for every generator item in the hub.

    And from this, I just got one suggestion for the generator-stats-plugin: What if you could do the same technique that you mentioned earlier within the plugin itself, those data you can then pass it through a variable, for example:

    genStats = [generatorStats("power-name", "power-hangman", "power-input-twister", ...)]

    And then, when you want to retrieve these data:

    The Power Name Generator has been viewed [genStats["power-name"].views] times and was edited [genStats["power-name"].lastEditTime].

    With that, everyone and not only me can use the names technique just by using the plugin. And thanks for the more descriptive explanation on the “connection stall” problem! 😊