Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

内存,cpu占用高! 用flv 播放h265和h264 #185

Open
LxbNNN opened this issue Apr 19, 2024 · 6 comments
Open

内存,cpu占用高! 用flv 播放h265和h264 #185

LxbNNN opened this issue Apr 19, 2024 · 6 comments

Comments

@LxbNNN
Copy link

LxbNNN commented Apr 19, 2024

No description provided.

@LxbNNN
Copy link
Author

LxbNNN commented Apr 19, 2024

开发电脑:macbook pro m1

config配置:
3701713521281_ pic

版本:1.7.3
3711713521297_ pic_thumb

内存和cpu情况:
内存会一直升高,cpu最高占用50%,测试的电脑有时最高会占用到70%(12代i5)
3751713521665_ pic

当使用了destroy() 方法后 内存会清理不完全 在空页面 内存任占用600m 左右 ,正常页面进入 大约在120m 左右

@LxbNNN LxbNNN changed the title 使用mpegts 用flv 播放👌65 使用mpegts 用flv 播放h265和h264 Apr 19, 2024
@LxbNNN LxbNNN changed the title 使用mpegts 用flv 播放h265和h264 内存,cpu占用高! 用flv 播放h265和h264 Apr 19, 2024
@LxbNNN
Copy link
Author

LxbNNN commented Apr 19, 2024

同时播放了9路视频

@wujisui
Copy link

wujisui commented Apr 24, 2024

你把这里设置 autoCleanupSourceBuffer:false; 后面又设置 autoCleanupMaxBackwardDuration:10; 是不是有问题?

@LxbNNN
Copy link
Author

LxbNNN commented Apr 24, 2024

你把这里设置 autoCleanupSourceBuffer:false;后面又设置autoCleanupMaxBackwardDuration:10;是不是有问题?

image
因为开启自动清理会报错,官方文档 autoCleanupSourceBuffer默认值也是false ,autoCleanupMaxBackwardDuration 到3分钟清理,我是直播,只是减少了清理的阈值,应该是没问题的,并且我观察内存,会在播一段时间降低一些,说明配置是生效的,随后才会逐步升高。

@zui4yi1
Copy link

zui4yi1 commented Jul 18, 2024

你把这里设置 autoCleanupSourceBuffer:false;后面又设置autoCleanupMaxBackwardDuration:10;是不是有问题?

image 因为开启自动清理会报错,官方文档 autoCleanupSourceBuffer默认值也是false ,autoCleanupMaxBackwardDuration 到3分钟清理,我是直播,只是减少了清理的阈值,应该是没问题的,并且我观察内存,会在播一段时间降低一些,说明配置是生效的,随后才会逐步升高。

应该要true吧

@thy486
Copy link

thy486 commented Aug 2, 2024

如果你是直播,那就不要强制 autoCleanupSourceBuffer 设置为 false,直播的默认值是 true, 会报错应该把报错信息拉出来

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants