内存泄漏问题

[liu86th]

运行一段时间自动崩了，去掉x.Free() 这个就不会崩，但是内存占用好大啊，部署到k8s中去的时候

[CNLHC]

I guess that the problem here is that you are trying to invoke x.Free() manually.

Actually, I add this line in order to make the golang GC to manage the underlying jieba memory which i consider the right way to write go program. #96

A quick fix is removing your manual invokation to the Free method and let the FInalizer do the free job.

My personal opinion is that the Free method should be private here. Because if gojieba keeps the Free method and rely on the user to manage the jieba memory, all the go objects that contain (directly or indirectly) the jieba instance will rely on the user to manage memory, which is not an ideal go pattern.

[mostcute]

double free or corruption (!prev)

[github-actions]

This issue has not been updated for over 1 year and will be marked as stale. If the issue still exists, please comment or update the issue, otherwise it will be closed after 7 days.

[yanyiwu]

这个问题和 Free() 双重释放/释放时机相关，已在后续版本修复（Free() 增加原子保护，NewJieba() finalizer 行为也已补齐）。

建议升级到最新版本 v1.4.7 后再验证。如果你在 v1.4.7 仍能稳定复现，请按最小复现代码重新开 issue，我会继续跟进。