When I use @uppy/compressor with the Dashboard, memory usage climbs by about 2x the size of uploaded files during the compression phase and remains at that level until uploads complete (after which the page reloads.)
Many of my app’s users need to upload >50 photos at once, and the high memory pressure seems to cause crashes for some folks. I’m also seeing some reports of lingering issues after users upload smaller numbers of photos (4-6), which has me wondering about a memory leak.
I’ve tried decreasing the parallel compression limit, but because the issue seems to be compressed images hanging out in memory until they’re uploaded, this hasn’t really affected the situation. Is there anything I can do to tweak the Compressor and restore decent performance, or is client-side compression just not going to be viable for my use-case?