Yes, It's a BLU RAY optical drive so I can watch blu ray movies on my PC Looks sexeh on my 50" HDR TV that doubles as a monitor!

Except that there's heavy DRM on those disks, to the point where I don't think you can watch recent ones under Linux.

Not just games.....
I dont know why a modern super fast computer can take longer to close a program than it did to open it??? Or especially closing webpages! I told it to close the webpage, What is there to think about? JUST F___ING CLOSE IT!!!!

It always left me wanting more, though, and i'd gladly shell out a few bucks for it.

The program is cleaning up. All that memory that's been malloc()ed has to be free()ed at some point, and that can take a lot of time sometimes. Plus, the program still has to close all open files. (Also, in the case of web browsers, some on-disk information, like cache and cookies, may need to be updated.)

Incidentally, I have seen some programs that actually don't bother to free() their malloc()ed memory when they quit, relying on the OS to take care of that.

(Before anyone mentions that this is C-centric, I should point out that programs written in other languages still have to allocate and free memory, even garbage-collected languages like Java (garbage collection isn't free, you know) and reference counted languages like Python. And then, of course, there's JavaScript, which is quite relevant to this situation.)

Well, that sounds reasonable, thanks, but the time delays to shut down a program/webpage is seriously inconsistent. You can do exactly the same thing you did yesterday, but the result can be vastly different.... you can do exactly the same thing for 6 months, then one day, out of nowhere, the computer decided "ok today i am going to take 30 seconds to close this program, even though i just spent the last 6 months closing it after 3 seconds every day".... "and tomorrow i will be back to closing it in 3 seconds every day".... "i just like to mix things up every now and then"

I suppose, i just get curious to what the computer is doing when it decided to take a long time to close something? i am like " I told it to close the program, WTF is it doing?" Fascinating?

Spectral Souls was notorious for being so poorly optimized that basically everything requiring disc access times. animations, text/portraits in cutscenes etc..

There are other factors that can cause timing to vary. For example, the computer could be busy doing something else at the same time (especially likely if you close multiple tabs at once). Another case is if some of the memory the tab is using is swapped to disk; this happens if programs try to use more memory than actually exists as RAM in the system; less recently used data is swapped to disk (typically to a swap partition or file), and if the program tries to access it later, the OS needs to read the data from disk in order to for the program to continue. In the case of closing a program (or browser tab), it's possible that some memory might be allocated, used for a bit, then not actually needed later (for example, the "back" button history; if you don't use it, it might be swapped to disk, but the system still has to keep track of it in case you decide to press the back button later). When you close it, suddenly the memory needs to be accessed so it can be cleaned up, and that triggers a page fault, causing the OS to have to read from the disk before the tab can finally be closed.

Note that this slow browser tab closing, at least for this reason, should be more likely if programs have used a large amount of RAM recently (for example, if the tab was open when you had a lot of tabs open).

(There's also, of course, the dreaded memory leak; when a process allocates memory and forgets about it without freeing it; this leads to issues where areas of memory are unused but the OS still thinks they're in use, which will slow down the system when it comes time to swap it out, and the unused memory might share a page with memory that's actually used. At least it's not as bad as the memory corruption that happens if a program uses memory it's already freed.)

Much of this behavior is non-deterministic, as it depends on what else is going on in the machine; hence why you might notice different behavior at different times.

Didn't mean to offend, just sharing my own experience.