你好开发者,为什么我用html发送19MB的rar格式,多次尝试一直无反应,请问问题出在哪里??
你好开发者,为什么我用html发送19MB的rar格式,选择19MB文件后,浏览器页面卡一下,然后再无动静,后续多次尝试一直无反应,请问问题出在哪里?感谢你的项目,后续可否增加exe版本?
Hello developers, why I sent a 19MB rar file in HTML format but it didn't work after multiple attempts. What's the problem?
Hello developer, why when I use HTML to send a 19MB rar format, after selecting the 19MB file, the browser page freezes for a while, and then nothing happens. After multiple attempts, there is still no response. What is the problem? Thank you for your project. Can you add an exe version in the future?
I probably need to make sure the error shows on the page instead of being hidden in the console...
For files in the ~20 MB range or larger, the browser is inconsistent about giving us a contiguous chunk of memory -- sometimes it works (after taking a few seconds), but it also can fail (what you're seeing, I think) with an out of memory (OOM) error.
It's pretty random in my experience, so you could try a different browser to see if that helps. Otherwise, the simplest thing is probably to split the file, send it in smaller pieces, and put it back together on the receiver side.
Can you add an exe version in the future?
Perhaps. I've been hesitant to make a pure native version (since I'd have to dev/test on an additional platform), but something like a webview wrapper is probably reasonable.
I've updated cimbar.js (and cimbar.org) to hopefully hit the OOM error less often. https://github.com/sz3/libcimbar/releases/tag/v0.6.3
Really? You're absolutely amazing. I'm going to give it a try right away. Thank you so much for your work.
---原始邮件--- 发件人: @.> 发送时间: 2025年10月17日(周五) 中午1:32 收件人: @.>; 抄送: @.@.>; 主题: Re: [sz3/libcimbar] 你好开发者,为什么我用html发送19MB的rar格式,多次尝试一直无反应,请问问题出在哪里?? (Issue #132)
sz3 left a comment (sz3/libcimbar#132)
I've updated cimbar.js (and cimbar.org) to hopefully hit the OOM error less often. https://github.com/sz3/libcimbar/releases/tag/v0.6.3
— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.***>