Hello Fedora Community,
I am currently experiencing one persistent problem with my website when it is accessed from a Fedora desktop, and I am hoping someone can help me determine whether the cause is related to Fedora, the browser environment, or something in the way my download jenny minecraft website is being rendered. The specific issue is that the website initially loads and operates normally, but after the page has been open and actively used for an extended period, the browser tab gradually becomes sluggish and eventually stops responding to user interaction. At the beginning of the session, scrolling, clicking buttons, opening menus, entering information, and navigating between different sections all work normally. After continued use, however, the page can become noticeably slower and eventually appear frozen, while the rest of the Fedora desktop continues working normally. Refreshing the website immediately restores normal behaviour, so the problem appears to be associated with the long-running browser session rather than the website being completely unavailable.
The website is a relatively interactive application that uses JavaScript to update parts of the interface dynamically without requiring a full page reload for every action. Users can move between sections, load additional content, interact with forms, and trigger various interface updates during a normal session. I have tried to reproduce the problem by using the download jenny minecraft website normally rather than performing any unusual or automated activity, and the issue seems more likely to occur after many repeated interactions. The page does not immediately fail when it is opened, and there is no single action that consistently causes the freeze. Instead, the application remains functional for a while and then gradually becomes less responsive. When the problem occurs, some clicks may take several seconds to register, scrolling may stop temporarily, and eventually the browser tab may stop responding altogether even though other applications on the Fedora desktop remain usable.
I have been monitoring the browser and system behaviour while trying to reproduce the problem, and one thing I have noticed is that browser resource consumption can increase during a long session. I have not yet been able to determine whether this is caused by a memory leak in my website’s JavaScript code or by the browser’s rendering environment on Fedora. I have checked the browser developer console and have not found an obvious JavaScript exception immediately before the page becomes unresponsive. The website’s backend also continues responding normally when tested separately, which suggests that the server is not simply becoming unavailable at the same time. Because the problem develops gradually rather than occurring immediately, I am interested in determining whether there is a browser or operating-system-level resource that could be accumulating while the website remains open and interactive.
