Update README.

ossrs · Jun 15, 2024 · 5b4cfad · 5b4cfad
1 parent a7ce6b6
commit 5b4cfad
Show file tree

Hide file tree

Showing 2 changed files with 4 additions and 0 deletions.
diff --git a/i18n/en-us/docusaurus-plugin-content-blog/2024-06-15-SRS-Smart-Pointer.md b/i18n/en-us/docusaurus-plugin-content-blog/2024-06-15-SRS-Smart-Pointer.md
@@ -17,6 +17,8 @@ Each stream on the SRS server has a Source object that manages the stream's life
 simple, SRS did not release the Source object; with a large number of streams, such as constantly changing streaming 
 addresses, this led to continuous memory growth and leaks.
 
+<!--truncate-->
+
 Previously, the workaround was to restart the service late at night. SRS supports [Gracefully Quit](https://github.com/ossrs/srs/issues/1579#issuecomment-587414898), 
 which restarts the service when there are no connections, but this did not completely solve the problem.
 

diff --git a/i18n/zh-cn/docusaurus-plugin-content-blog/2024-06-15-SRS-Smart-Pointer.md b/i18n/zh-cn/docusaurus-plugin-content-blog/2024-06-15-SRS-Smart-Pointer.md
@@ -15,6 +15,8 @@ custom_edit_url: null
 每个流在SRS服务器上有个Source对象，用于管理流的生命周期。为了逻辑和代码简单，SRS一直没有释放Source对象；在流特别多的情况下，
 比如不断更换推流的地址，会导致内存不断增长和泄露。
 
+<!--truncate-->
+
 之前绕过这个问题的办法，就是半夜三更重启服务。SRS支持[Gracefully Quit](https://github.com/ossrs/srs/issues/1579#issuecomment-587414898)，
 会在没有连接时重启服务，但是这个方法并没有彻底解决这个问题。