You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
migrated from Bugzilla #75287
status NEEDINFO severity major in component intel for ---
Reported in version unspecified on platform x86-64 (AMD64)
Assigned to: haihao
In h264encode, we observe that memory usage increases as the program proceeds. For large files, this results in unreasonably large memory usage.
Example case:
Input: 18G yuv file
Output: 3.3G h264 video
run with valgrind using the massif tool:
$ valgrind --tool=massif --stacks=yes /usr/local/bin/h264encode --srcyuv output2.yuv -framecount 0 -f 25 -o massif_test_out.mp4
There is a malloc at i965_drv_video.c:1671 that accounts for 92.58% of memory usage at the peak. This call creates a buffer which has a reference count on it. When the reference count hits 0, the memory is cleared. Many of the buffers stored in this way never have their reference counts set to zero during encoding. As a result, the memory usage keeps growing during encoding. On completion, all of this memory is freed, so a simple valgrind run does not find this leak.
migrated from Bugzilla #75287
status NEEDINFO severity major in component intel for ---
Reported in version unspecified on platform x86-64 (AMD64)
Assigned to: haihao
Original attachment names and IDs:
On 2014-02-20 22:59:05 +0000, Bryan Christ wrote:
On 2014-03-24 01:43:46 +0000, haihao wrote:
On 2014-03-24 17:39:45 +0000, Bryan Christ wrote:
On 2015-11-26 03:08:58 +0000, haihao wrote:
The text was updated successfully, but these errors were encountered: