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
I am currently tracking a memory leak issue. It is not yet clear whether the leak originates from OpenVINO or our own program. However, during the tracking process, I found that even if we only call compile_model, the memory usage keeps increasing for several hours before stabilizing. Although the memory growth eventually stabilizes, this issue makes it difficult for us to identify the memory leak problem we are looking for. I would like to know how to stabilize OpenVINO's memory usage quickly to facilitate debugging the memory leak issue
and some logs:
<style>
</style>
2024-06-24 20:30:00
131912
2024-06-24 20:30:05
131912
2024-06-24 20:30:10
131912
2024-06-24 20:30:15
131912
2024-06-24 20:30:20
131912
2024-06-24 20:30:25
131912
2024-06-24 20:30:30
131912
2024-06-24 20:30:35
131912
2024-06-24 20:30:40
133948
2024-06-24 20:30:45
133948
2024-06-24 20:30:50
133948
2024-06-24 20:30:55
133948
2024-06-24 20:31:00
133948
2024-06-24 20:31:05
133948
2024-06-24 20:31:10
137876
2024-06-24 20:31:15
137876
2024-06-24 20:31:20
137876
2024-06-24 20:31:25
137876
2024-06-24 20:31:30
137876
2024-06-24 20:31:35
137876
2024-06-24 20:31:40
141948
2024-06-24 20:31:46
141948
2024-06-24 20:31:51
141948
2024-06-24 20:31:56
141948
2024-06-24 20:32:01
141948
2024-06-24 20:32:06
141948
2024-06-24 20:32:11
141948
2024-06-24 20:32:16
141948
2024-06-24 20:32:21
141948
2024-06-24 20:32:26
141948
2024-06-24 20:32:31
141948
2024-06-24 20:32:36
141948
2024-06-24 20:32:41
141948
2024-06-24 20:32:46
141948
2024-06-24 20:32:51
141948
2024-06-24 20:32:56
141948
2024-06-24 20:33:01
141948
2024-06-24 20:33:06
141948
2024-06-24 20:33:11
141948
2024-06-24 20:33:16
141948
2024-06-24 20:33:21
141948
2024-06-24 20:33:26
141948
2024-06-24 20:33:31
141948
2024-06-24 20:33:37
141948
2024-06-24 20:33:42
142096
2024-06-24 20:33:47
142096
2024-06-24 20:33:52
142096
2024-06-24 20:33:57
142096
2024-06-24 20:34:02
142096
2024-06-24 20:34:07
142096
2024-06-24 20:34:12
142096
2024-06-24 20:34:17
142096
2024-06-24 20:34:22
142096
2024-06-24 20:34:27
142096
2024-06-24 20:34:32
142096
2024-06-24 20:34:37
142096
2024-06-24 20:34:42
144128
2024-06-24 20:34:47
144128
2024-06-24 20:34:52
144128
2024-06-24 20:34:57
144128
2024-06-24 20:35:02
144128
Step-by-step reproduction
No response
Relevant log output
No response
Issue submission checklist
I'm reporting an issue. It's not a question.
I checked the problem with the documentation, FAQ, open issues, Stack Overflow, etc., and have not found a solution.
There is reproducer code and related data files such as images, videos, models, etc.
The text was updated successfully, but these errors were encountered:
@bwang30 Please also share some other information so that we can reproduce faster.
CPU model:
Software information
-- OS version (include kernel version for Linux): Ubuntu 20.04 (LTS)/kernel version?
-- OV version: 2024.2 or master branch(which commit ID have you tried?)
-- How OV is built or where the OV is downloaded?
Questions
-- Reproduce only with particular platform or model or SW version?
-- What is latest "work as expectation" configurations?
OpenVINO Version
2024.2, 2024.3
Operating System
Ubuntu 20.04 (LTS)
Device used for inference
CPU
Framework
None
Model used
No response
Issue description
I am currently tracking a memory leak issue. It is not yet clear whether the leak originates from OpenVINO or our own program. However, during the tracking process, I found that even if we only call compile_model, the memory usage keeps increasing for several hours before stabilizing. Although the memory growth eventually stabilizes, this issue makes it difficult for us to identify the memory leak problem we are looking for. I would like to know how to stabilize OpenVINO's memory usage quickly to facilitate debugging the memory leak issue
and some logs:
<style> </style>Step-by-step reproduction
No response
Relevant log output
No response
Issue submission checklist
The text was updated successfully, but these errors were encountered: