Why closing Firefox takes two minutes with constand HDD access? Closing a program requires just a few writes into process tables and mark its pages free. That a few microseconds on modern CPUs. So why few minutes? During shutdown Firefox even manages to increase its working set, loading stuff from swapfile. That is some retarded design out of communist Gulag, where they force North Korean programmers to write rock launch code for a bowl of rotten rice.
Name:
Anonymous2018-03-05 0:00
Read the fucking source.
Name:
Anonymous2018-03-05 0:07
It's writing the contents of its configuration to disk. It has a lot of configuration settings to work through.
>>4 I'm not so sure about that volume. There's enough volume that it takes around one minute of disk writing.
Name:
Anonymous2018-03-05 6:08
I remember way back when (<2007) it still had this same problem. You couldn't reopen it immediately after closing it because some files were locked. Amazing it still happens to this day.
Some bugs are just so deep seated you'd have to rewrite the whole thing to get rid of it.
Name:
Anonymous2018-03-05 7:43
No, that's how browsers work. Especially with a multi-process model
Name:
Anonymous2018-03-05 9:43
OP are you the guy for whom 50MiB was actually a noticeable chunk of the disk size? You might not want to use contemporary browsers on your 2001 Dapper Drake xubanto box.