I don't know if there is, but it feels like the email protocol problem.

Like, while the protocol sucks in many, many ways, it would take something revolutionary to replace it because it's everywhere.

It's been around so long that everything talks the protocol, the binaries that handle it are mature and stable.

Then you have to ask: what would you replace it with? It does the job it's designed to do very well. There's nothing the matter with the protocol, and it's still fit-for-purpose.

That doesn't mean there aren't problems - spam, bad actors, and so on, but ultimately that's not the fault of the protocol (though, maybe, for email, people have been arguing about protocol-level ways of dealing with spam for years).

I don't have an answer, but I feel like there should be one, but I doubt the is.

The last time I saw this was on a slow-failing HDD.

Check a quick fsck might get you a few answers. You can find more info in the Linux manual. It could just be one or two bad blocks that you can recover and fix the problem (though, ofc, it’s time to backup your data).

The other, slightly unusual time I’ve seen it is with mixed RAM. 16gb made of 2x6g and then 2x4gb did some real odd things to the system. If it’s not the disk, and your box will boot with one stick of ram, try it to see if it fixes the issue. It could be that your RAM speeds are off (or your like me and just put two sticks you had lying around, and it basically worked until it didn’t).

An outlier, that I’ve not seen on modern machines is io/wait for a CD-ROM to spin up, even if your not accessing the CD-ROM. Normally caused by bad cabling. Based on the age of your machine, this is unlikely, but it might be worth unplugging devices to see if one is bad and not reporting properly.

This is, if course, assuming dmsg is empty

Final thought: see if your running SELinux. If you are, turn it off and try again. Those policies are complex, and something installed in a non-standard place could be causing SELinux to slow IO as it fills your logs with warnings.

Hope that helps,

For those that find this question is asking something that they are also struggling with, the answer was the ‘embed’ tag

MDN link

You will need to place the element into a structural holder (eg div), and remove and recreate the element in JavaScript to get it to vanish and reappear if you want it to reload on show.

Pages loaded in this way do not inherit CSS theming, except background colour (if no background colour set). It does pick up @media settings, but only from the browser. This is intended behaviour.

Ultimately, to get the full functionality, I am going to have to redesign these items to be part of a single page, loading the data in piecemeal. However, this fix gets me a functional way of achieving something I need quicker than a redesign.

Thanks,

-BX

That works except for the pages loaded in, which do have the JavaScript tags at the end of their respective pages, however, one claims that the variables being set at the top of the script are not accessible

Yes,

I’m aware it’s a use case for an iframe. However, I’m looking for a way to do it without an iframe. Most of the logic is there, just that there are these anomolies with the JavaScript variables.