But could you do the test to put 3760, and tell us if it works, or if at startup it tells you that you have an erroneous value and puts it by default.?
Since 3072 (2048 in old versions of OS/2) is the maximum allowable, 3760 should always tell you that it is invalid (does, for me). 3072 doesn't always work either, but it won't tell you that it is an invalid number. I don't remember what happens, but it isn't good. I always use 2560 (but 2760 should also work), just so I don't have to figure out if machines work with 3072, or not. 2560 seems to be sufficient for my needs, and leaves me with 1270944 bytes of upper shared memory (varies as I use it), after everything is loaded.
I have never seen anything drop upper shared memory below 1000000 bytes, yet (I may have missed it). Lower shared memory, on the other hand, is at 217856, with most things loaded. I have seen that drop to zero (with resulting catastrophe), when something (usually multiple videos in Firefox), starts eating it. However, with the Firefox TURBO thing, I haven't seen that happen recently. I also turn off media.autoplay.enabled in Firefox about:config, which has helped a lot. It means one extra click to play a video that I do want to play, but the rest don't start automatically.