You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This set of stacks shows the issue. Fortunately this should be easy to fix: before we schedule any trimToByteSize: call, we should check a global BOOL to see if another trim is either scheduled, or currently running.
This would need a global lock, but it should be rarely contended. We could later use that global lock to also protect access to the trash, allowing us to delete the trash directory as one unit and then recreate the trash directory before any other items are moved to the trash.
This set of stacks shows the issue. Fortunately this should be easy to fix: before we schedule any trimToByteSize: call, we should check a global BOOL to see if another trim is either scheduled, or currently running.
This would need a global lock, but it should be rarely contended. We could later use that global lock to also protect access to the trash, allowing us to delete the trash directory as one unit and then recreate the trash directory before any other items are moved to the trash.
The text was updated successfully, but these errors were encountered: