Replies: 3 comments 11 replies
-
First off, why is the latest |
Beta Was this translation helpful? Give feedback.
-
Second question, why do you need to provide a Also, do you confirm that if you return right at the beginning of your |
Beta Was this translation helpful? Give feedback.
-
After updating the code to ffmpeg 7.0 and go-astiav, I encountered the same issue again. I now confirm that the memory leak occurs at CreateSoftwareScaleContext. I found others online who faced the same problem and provided their solutions, but I'm not sure if these would be effective for go-astiav as well. Issue with sws_getContext Function Not Releasing Memory After repeated investigations, I discovered a memory leak issue with the sws_getContext function. Strangely, even though sws_freeContext(pa->sws_ctx) has been called in the program to release the memory, it still leaks. Later, I found a function called sws_getCachedContext(). After replacing it, the memory leak was resolved!!! sws_getCachedContext
|
Beta Was this translation helpful? Give feedback.
-
As a Go beginner, this issue has troubled me for three days. I have tried using both
SoftwareScaleContext
andFilters
to convert frames into images. Despite my efforts to understand the code in the demo, I still haven't achieved the result I want. Currently, I can successfully transcode usingSoftwareScaleContext
, but as soon as I do, the memory usage keeps increasing, and I can't figure out which part of the code is causing the problem. When trying theFilters
approach, I've spent the whole day without making any progress. Can someone help me fix the code below so that both methods work properly?I'm currently using the
go-astiav
version from then6.1.1
branch. As for why I'm not using the latest version, it's because I'm working withffmpeg-rockchip
, and the latest 7.0 branch offfmpeg-rockchip
is not compatible withgo-astiav
.Beta Was this translation helpful? Give feedback.
All reactions