Bug Report Streams for 40 seconds then memory leak?

BluePhase

New Member
Yesterday I decided to get a new storage device which is an SSD 120GB Vertex 3. I used to run OBS on a 2 TB seagate drive and that ran fine. But now when I run OBS on my new drive, it runs for about 40 seconds, the stream color indicator flickers then turns red. Then either frames completely drop at an insane rate or stream times-out and attempts to reconnect. I haven't had this issue before and I tried 2 versions of OBS but still seem to get it. I have overclocked my computer months ago but that wasn't an issue with my old hard drive. Near the end of the log you can see that it says "memory leaks were detected." I'm assuming that is an issue with maybe faulty RAM, but I am not entirely sure. I played around with the settings and tried to lower all the values but it still happens.

Code:
Open Broadcaster Software v0.466a - 32bit (´・ω・`)
-------------------------------
CPU Name: Intel(R) Xeon(R) CPU           E5649  @ 2.53GHz
CPU Speed: 3705MHz
Physical Memory:  4095MB Total, 4095MB Free
stepping id: 2, model 12, family 6, type 0, extmodel 1, extfamily 0, HTT 1, logical cores 12, total cores 6
Windows Version: 6.1 Build 7601 S
Aero is Disabled
------------------------------------------
Adapter 1
  Video Adapter: NVIDIA GeForce GTX 560 Ti  
  Video Adapter Dedicated Video Memory: 1025966080
  Video Adapter Shared System Memory: 3221372928
=====Stream Start=====================================================================
  Multithreaded optimizations: On
  Base resolution: 1920x1080
  Output resolution: 1920x1080
------------------------------------------
Loading up D3D10...
------------------------------------------
Audio Encoding: AAC
    bitrate: 128
Using graphics capture
------------------------------------------
Video Encoding: x264
    fps: 60
    width: 1920, height: 1080
    preset: veryfast
    CBR: no
    max bitrate: 1000
    buffer size: 1000
    quality: 5
------------------------------------------
SharedTexCapture hooked
Using RTMP service: Twitch / Justin.tv
  Server selection: rtmp://live-3c.justin.tv/app
bufferTime: 1876, outputRateWindowTime: 1000, dropThreshold: 2376
RTMPPublisher::BufferedSend: Buffer is full (143474 / 144384 bytes), waiting to send 3663 bytes
RTMPPublisher::BufferedSend: Buffer is full (143474 / 144384 bytes), waiting to send 3663 bytes
RTMPPublisher::SocketLoop: Aborting due to FD_CLOSE, error 10053
Total frames rendered: 3844, number of frames that lagged: 1 (0.03%) (it's okay for some frames to lag)
Number of b-frames dropped: 10 (0.16%), Number of p-frames dropped: 50 (0.78%), Total 60 (0.93%)
=====Stream End=======================================================================
=====Stream Start=====================================================================
  Multithreaded optimizations: On
  Base resolution: 1920x1080
  Output resolution: 1920x1080
------------------------------------------
Loading up D3D10...
------------------------------------------
Audio Encoding: AAC
    bitrate: 128
Using graphics capture
------------------------------------------
Video Encoding: x264
    fps: 60
    width: 1920, height: 1080
    preset: veryfast
    CBR: no
    max bitrate: 1000
    buffer size: 1000
    quality: 5
------------------------------------------
SharedTexCapture hooked
Total frames rendered: 132, number of frames that lagged: 1 (0.76%) (it's okay for some frames to lag)
Number of b-frames dropped: 0 (0%), Number of p-frames dropped: 0 (0%), Total 0 (0%)
=====Stream End=======================================================================

Profiler results:

==============================================================
frame - [100%] [avg time: 5.675 ms] [avg calls per frame: 1] [children: 92.1%] [unaccounted: 7.93%]
| scene->Preprocess - [0.0529%] [avg time: 0.003 ms] [avg calls per frame: 1]
| video encoding and uploading - [92%] [avg time: 5.222 ms] [avg calls per frame: 1] [children: 42.6%] [unaccounted: 49.4%]
| | CopyResource - [0.264%] [avg time: 0.015 ms] [avg calls per frame: 0]
| | conversion to 4:2:0 - [0.634%] [avg time: 0.036 ms] [avg calls per frame: 0]
| | call to encoder - [41.6%] [avg time: 2.359 ms] [avg calls per frame: 0]
| | sending stuff out - [0.106%] [avg time: 0.006 ms] [avg calls per frame: 0]
==============================================================

Memory Leaks Were Detected.
 

BikeMan

New Member
Having the EXACT same issue!! Only I have made NO changes to my computer! Start stream, then it flickers yellow and redd and the frame drops number starts ticking up at an incredible rate! I think something is interfering with the capture hook or something. I have tried multiple versions of OBS, and different settings of every variety you can imagine. It still does it. Perhaps there is a way to fully remove OBS even from the registry of Windows 7 and try a new install? Even if I uninstall the new version have the same settings...

Also for clarity I have been streaming successfully with OBS for 3 months now and I love it. This is my first issue, please help, I cannot go back to Xsplit, it is nightmarish on my CPU!
 

Lain

Forum Admin
Lain
Forum Moderator
Developer
hmm, appreciate the info about the memory leak. as for the dropped frames, not entirely sure, usually should just mean network congestion.
 

BluePhase

New Member
Jim said:
hmm, appreciate the info about the memory leak. as for the dropped frames, not entirely sure, usually should just mean network congestion.

Thanks for the reply Jim, I will look into it on my end as well. I will test different RAM, unclock my CPU, and check network settings/call ISP. Hopefully I can pinpoint the issue to some specific cause and will get back to this post.

As for Internet speeds,
2462220878.png
 

BluePhase

New Member
It appears that the problem was definitely network. I unclocked CPU and switched RAM but memory leak was still being displayed. I reset the network a few times and sure enough it was fixed.
 

retbergen

Member
why do you cap the bandwith at 1000 while going full HD at 60 frames? That is asking for the impossible + enourmous compression stress. I see no reason why you shouldnt be able to increase it to 2 ot 3000, as your upload speed is 5000. This is probably not related to your problems, still its a bad setting.
 

BluePhase

New Member
As I said previously, that isn't my main settings. I normally have the max bitrate set to about 3500 kb but I was just testing under 1000 kb connection..
 
Top