fd_batch unref vs resource unref locking issues..
currently __fd_batch_destroy() does the rather questionable thing of dropping screen lock in order to unref pipe_resources.. mainly because resource_destroy path needs to aquire lock, and we don't have recursive locks.
Probably a better approach is an fd_resource_reference_locked() alternative to pipe_resource_reference() in paths where screen lock is held?
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information