Up to date is actually irrelevant. Yes, old browser versions can cause problems when eBay changes their website code to use newer web technologies that the older browsers can't cope with (as those technologies or features were not built into the older browsers), but newer browsers that update all the time can cause as many or more problems when the browser maker changes something that is incompatible with existing unchanged eBay code.
eBay only uses and saves a maximum approx 2.5MP (1600x1600) of image information. When you upload a giant 40MP image, eBay resizes it down to 1600 pixels on longest side and stores that - the giant upload is discarded. That 1600 x ? pixel image becomes the source for smaller resized images and thumbnails used in various places on eBay.
Yes, every manipulation of an image results in some loss of quality, but at the sizes displayed on webpages, any resizing you might do to your original images before uploading would not be visible to the eye. The problem comes in when eBay servers are stressed by accepting the giant upload and then having to spent inordinate amounts of resources and time performing the resizing processing.
Remember, image size goes as the square. A 1600x1200 image is 2MP An image twice as large on a side is 3200x2400 image and is 8MP - 4 times larger in terms of number of pixels (and roughly filesize depending on the compression protocol). Takes 4 times as long to upload, 4 times as long for eBay to process, requires 4 times as much memory on the eBay machines to load for processing (again approx and depends on the algorithms)
Whatever you are uploading may be pushing some soft eBay defined upload filesize limit or upload time limit and thus failing.
Uploading images resized to no more than 5 MP (2560x1920 for example) is still overkill, but should be more than sufficient for what will be displayed on eBay after they do their resizing, and shouldn't choke the upload servers.
Slowing down, stepping back, trying alternatives and workarounds is always a good idea.