fengyuanchen/cropperjs

Memory not released in Safari when editing multiple images

Open

#963 建立於 2022年7月20日

在 GitHub 查看
 (0 留言) (1 反應) (0 負責人)JavaScript (12,111 star) (2,388 fork)batch import
help wantedquestionv1

描述

When multiple images are uploaded, page memory is adding up and never released. Especially when using mobile devices, this results in the WebView to eventually reload (this is especially problematic when Cropper.js is implemented in a page with other information, as that information would then be lost).

To Reproduce: While monitoring memory usage in Safari's Web Inspector 1 - Upload image 2 - Upload another image ..n - Upload another image

Screenshots cropperJS 2 cropperJS

Tested on:

貢獻者指南

技術棧
javascript
領域
frontend
議題類型
bug
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-3 hours
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
Basic JavaScriptMemory leak debuggingSafari Web Inspector
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
30
研究方向
Investigate the memory management in cropperjs, particularly during image loading and canvas operations. Focus on Safari's memory handling. Review the image cropping loop to see if objects are properly dereferenced. Consider using Safari's Timeline to track allocations.