memos
memos copied to clipboard
Memory Overflow 内存溢出
Describe the bug
更新新版本后,会导致docker内存溢出
After updating to a new version, docker memory will overflow.
旧版本中(0.18),在输入框中插入已上传好的图片链接,直接可以发布,而在新版本,一提交链接会导致小内存机器内存溢出,从而直接导出服务器死机重启,docker中显示最高可到达近1GB,而日常正常多人使用则不会超过100MB。
In the old version (0.18), you can insert the uploaded image link in the input box and publish it directly. However, in the new version, submitting the link will cause the memory of the small memory machine to overflow, thus directly exporting the server to crash and restart. Docker displays the highest It can reach nearly 1GB, but normal daily multi-person use will not exceed 100MB.
以下小问题可能为个人设置:宝塔部署的docker 最新版本memos 0.19.1 服务器重启后 不会自动开启该容器(其他容器均开启)
The following small problems may be due to personal settings: the latest version of docker deployed by Pagoda, memos 0.19.1, will not automatically open the container after the server is restarted (other containers will be opened)
Steps to reproduce
1.在输入框中插入已上传好的图片链接 2.一提交链接会导致小内存机器内存溢出 3.直接导出服务器死机重启
The version of Memos you're using
0.19.1
Screenshots or additional context
No response
Issue is not in English. It has been translated automatically.
Title: Memory Overflow memory overflow
那只能说明你的机器内存太小了///我的可以达到4G 狗头笑
Issue is not in English. It has been translated automatically.
That only means that your machine's memory is too small///Mine can reach 4G Dog-headed smile
刚刚换了个大内存机器,直接跑满4G,这个限制应该是默认的容器内存限制 换句话说,直接跑满了,直接溢出(手动狗头)
Issue is not in English. It has been translated automatically.
I just changed to a large memory machine and ran directly to 4G. This limit should be the default container memory limit. In other words, it runs directly to full capacity and directly overflows (manual dog head)
使用最新的0.19.1版本,刚开始点击加载列表会卡死,页面无响应,现在发布一些memo之后竟然正常了.不知道是什么操作
Issue is not in English. It has been translated automatically.
Using the latest version 0.19.1, when I first clicked to load the list, it would get stuck and the page would become unresponsive. Now, after publishing some memos, it is normal. I don’t know what the operation is.
Try upgrading to v0.19.1 https://github.com/usememos/memos/releases/tag/v0.19.1