Question / Help Number of memory leaks: X

Suslik V

Active Member
I see. I was wrong. And if no sources (empty scene)? Still leak?

Edit: It's look like browser source causes leakage. I can reproduce now.

Edit 2: Just enough to delete obs-browser.dll (to remove the plugin load) and voila! No leakage when OBS Studio started/closed (log: 2017-01-13 13-18-48.txt).

Edit 3: the leakage starts happening since v0.14.1

Edit 4: probably browser plugin v1.20 (obs-browser-1.20) doesn't have the leak, but v1.21 has one (obs-browser-1.21)

Edit 5: the leakage was introduced with this commit: https://github.com/kc5nra/obs-browser/commit/c717c53bffe8e4ee407d2c0efef1bec334fd4dcb
 

Attachments

  • 2017-01-13 13-02-00.txt
    8.9 KB · Views: 35
  • 2017-01-13 13-04-57.txt
    8.9 KB · Views: 35
  • 2017-01-13 13-18-48.txt
    8.6 KB · Views: 30
Last edited:

Suslik V

Active Member
Generally - only by modifying the code. If my programming skills enough to resolve this, I could make a new commit to change current behavior and resolve the single leak. If not - someone else could make changes to the code to resolve the issue. It's open source by the way.
 

Suslik V

Active Member
@Christina13 you have no facts that you have the same, because topic starter has perfect timing:
Code:
01:30:34.663:  ┣tick_sources: min=0.002 ms, median=0.097 ms, max=379.249 ms, 99th percentile=4.26 ms
01:30:34.663:  ┣render_displays: min=0.001 ms, median=0.269 ms, max=355.566 ms, 99th percentile=0.988 ms
01:30:34.663:  ┗output_frame: min=0.092 ms, median=0.334 ms, max=98.627 ms, 99th percentile=1.172 ms
and you are not.
 
Top