Closed #511.
--
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
https://github.com/savonet/liquidsoap/issues/511#event-1798813522--
Check out the vibrant tech community on
Ok, awesome, thks! Gonna close this one and re-open. You might want to install
the `libgstreamer0.10-0-dbg` package, this would allow `gdb` to also show the
code lines where these are coming from.
--
You are receiving this because you commented.
Reply to this email directly or view it on
You prolly need to run it as `root`. Also, if you're inside docker you need
special options:
```
docker --cap-add=SYS_PTRACE --security-opt seccomp=unconfined ...
```
--
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
Hmm, I get ```ptrace: Operation not permitted.```
--
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
Thanks! Would you mind sending me a `gdb` backtrace? You can attach to the
running process:
```
% gdb
> attach
> thread apply all bt
```
Once I get this, I'll close this issue and open a new one with these info.
Thks!
--
You are receiving this because you commented.
Reply to this email
I'm gonna try my best to give a shot at recompiling for windows so you can
test.
Gilou, do you have anything to report on win32? p's issues seem pretty
severe, do you have similar problems?
2018-08-19 18:11 GMT-05:00 p· g··· :
> does this huge onset of latest development mean that we're
Yeah that's what I'm thinking. I'd love to see those logs..
--
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
Hmm, even though the on-screen logging is much more verbose, there is nothing
written to file ..
But also I don't see anything added to the log when this stale situation
occurs. (it just says 'finished with ..')
Also the LS process does still respond, I can connect over telnet! it then says
Ah yes sorry, will run again with this setting!
--
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
Any more info with `set("log.level",5)`?
--
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
https://github.com/savonet/liquidsoap/issues/511#issuecomment-414204988--
Check
@toots same result btw. after some time LS just sits idle and unresponsive.
Some log:
```2018/08/20 01:50:41 [random(dot)pl:3] Finished with
"/media/video/random/somevid.mp4".
2018/08/20 01:50:41 [decoder:3] Method "GSTREAMER" accepted
"/media/video/random/anothervid.webm".
2018/08/20 01:50:41
It means that we're working on fixing a particular problem right now.
Hold your horses with your list of requests. There can be other reports on this.
--
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
does this huge onset of latest development mean that we're also about to have a
win32 build without a memory leak, long file skipping issues and with properly
working terminal?!
cheers,
p
--
Check out the vibrant tech
Ok it's running (updated all repos and submodules).
Lets see how long it lasts :D
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Ok, you might want to test again (I know!) with the latest code. I've made more
changes to handle message bus differently. It still looks stable on my end
(including with your code).
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on
Any logs? Make sure you set `set("log.level",5)`
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
ok not sure what happened but I'm no longer getting output from LS. process is
still running and using memory. no cpu usage whatsoever.
can't do a ```ctrl+c``` either (I updated ocaml-duppy so this did work again)
--
You are receiving this because you are subscribed to this thread.
Reply to
Can you try your test-script but with my videoconvert and audioconvert settings?
that's:
```
video_pipeline=
"videoconvert ! x264enc bitrate=2000 ! video/x-h264,profile=baseline !
queue ! mux.",
audio_pipeline=
"audioconvert ! voaacenc bitrate=44100 ! queue ! mux.",
```
Yes I have it running with my original playlists and queues. Will let in run
for a while to see what happens to the memory :)
What I can tell so far is that when running ```output(dot)gstreamer.skip```
that the memory only changes per video (higher or lower), but doesn't actually
keep
You need to update `ocaml-duppy` to fix this, these are changes I pushed
yesterday :-)
Good news about the script. If I test yours it fails because there's no `rtmp`
server to connect to. Gonna see if I can get a better logging for gstreamer.
Can you let it run for a while and report? Memory
Ok, I'm not trying (debian stable gstreamer) with your output stage (except
with the rtmpsink) and it works!
So the only difference is the ```videoconvert``` and ```audioconvert``` parts.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view
This, which is like the minimum I want to be able to run (can of course make a
more minimal version)
```
set("server.telnet.bind_addr", "127.0.0.1")
set("server.telnet.port", 1234)
set("server.telnet", true)
set("log.file.path", "/media/log/playvideo.log")
set("frame.video.width", 888)
What's your test script?
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/savonet/liquidsoap/issues/511#issuecomment-414127816--
(with latest current sources same result btw)
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Is that with gstreamer ```1.10.4``` or ```1.14.2``` ?
btw I was missing a bunch of plugins and dependencies on my manual compile of
```1.14.2``` but even when all those where resolved I got
```
...
2018/08/18 14:17:31 [output(dot)gstreamer:1] Got ill-balanced activations (from
You request probably cannot be resolved. Try using a `playlist` and report the
logs you've got.
I'm happy to report that with the latest code it seems that memory usage is
under control now. Release is imminent to any quick testing and report would be
gladly received!
--
You are receiving
Hmm, I just built and installed gstreamer ```1.14.2``` and LS crashes:
```
$ liquidsoap test.liq
2018/08/18 01:02:43 >>> LOG START
2018/08/18 01:02:43 [main:3] Liquidsoap
I can reproduce, looks like it goes away with `1.14.2`. I've posted it on their
mailing list.
I still memory growing, tho, just at a much slower pace. Will keep
investigating..
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on
Ok, it 'seems' stable, but it's not actually playing any video.
Memory usage is super low (way lower than I would expect minimum to be).
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
My bad! Try again? :-)
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/savonet/liquidsoap/issues/511#issuecomment-413915618--
Ok, thanks. I've reverted some of the recent changes. Mind trying again the
latest code?
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
And then:
```
(gdb) continue
Continuing.
Thread 36 "liquidsoap" received signal SIGSEGV, Segmentation fault.
__memmove_avx_unaligned_erms () at
../sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S:242
242 in ../sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S
```
--
You are
```
% gdb /path/to/liquidsoap
> r
(program crashes)
> thread apply all bt
```
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Backtrack? I've tested with `Gstreamer 1.14.2` on Debian unstable/testing..
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Full log with just a single test file:
```
$ liquidsoap test.liq
[0/1992]
2018/08/17 09:55:50 >>> LOG START
Ok, pulled latest ocaml-gstreamer and liquidsoap. Reinstalling both ..
segfault :(
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Ok, ok. Let's try this again.. I've pushed more change and it seems stable now
on my debian build :-)
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Hahaha, that must be the very stable memory usage then .. (I thought it was a
bit low)
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
I lied :-) It's not working but I'm not sure what the issue is yet. To use my
example, switch back to `voaacenc` but I'm pretty sure you're gonna face the
exact same issue.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Hmm, that's really odd then ..
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
It works here on debian/sid with GStreamer 1.10.4 0..
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Sorry debian stable.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/savonet/liquidsoap/issues/511#issuecomment-413652320--
Check
(of course I'm on debian stable with this box .. I can try upgrading to
testing. don't feel like compiling all of gstreamer myself :P)
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
1.10.4-1
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/savonet/liquidsoap/issues/511#issuecomment-413647749--
Check out the
What's your version of `gstreamer`?
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Hah! I never would've figured this out!
Everything installed now in the fresh ocaml environment.
testing ...
And fails with a whole bunch of:
```
(Liquidsoap:20280): GStreamer-CRITICAL **: gst_mini_object_unref: assertion
'mini_object->refcount > 0' failed
(Liquidsoap:20280):
Ho weird. The `camlp4` optional stuff is being compiled. I'll have to look at
it. Meanwhile, you can fix this by install `camlp4`.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Nope. Made a fresh .opam switch with 4.07.0 and when pinning duppy I get:
```
dreamer@streamer:~/ocaml-duppy$ opam pin add . -y
duppy is now path-pinned to /home/dreamer/ocaml-duppy
[duppy] /home/dreamer/ocaml-duppy/ synchronized
[duppy] Installing new package description from
Yes, it also seems duppy doesn't want to build with opam 4.07.0
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
And also execute `opam update`
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
You've pinned everything marked above?
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Ok this is weird, I upgraded ocaml with ```opam switch 4.07.0``` and then
reinstall the packages but I just get:
```
Sorry, no solution found: there seems to be a problem with your request.
No solution found, exiting
```
--
You are receiving this because you are subscribed to this thread.
Ok, need all these sources with --recursive of course. and liquidsoap is
without the 'ocaml-' ;)
But, I need a newer ocaml now (have 4.02.3 and need >=4.03 ...)
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Memory use seems pretty steady here:
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Ok, I'll try all of these straight from source then :)
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
My output stage:
```
output.gstreamer.audio_video(
video_pipeline=
"videoconvert ! gdkpixbufoverlay location=/media/logo.png offset-x=768
offset-y=20 ! x264enc bitrate=2000 ! video/x-h264,profile=baseline ! queue !
mux.",
audio_pipeline=
"audioconvert ! voaacenc
Yes, I recompiled both.
```
dreamer@streamer:~$ opam reinstall gstreamer
=-=- Synchronising
Have you recompiled `ocaml-gstreamer` and `liquidsoap`? The following works
great here:
```
output.gstreamer.audio_video(
video_pipeline=
"videoconvert ! x264enc bitrate=3500 speed-preset=ultrafast !
video/x-h264,profile=baseline ! queue ! mux.",
audio_pipeline=
"audioconvert !
Huh. Trying with your code.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Hmm, segfaults after couple seconds.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Ok, hold your breath, I think I've found and fixed the issue.. Mind trying
again with the last commit above? :-)
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Nervermind.. Bad news: there still are mem leaks. Good news: I can reproduce :-)
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Ok, thanks for trying. Would you mind trying again with the latest changes?
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Yes, left it running for a while and oomkiller came by to shoot it down :(
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Can you confirm a longer term trend? When I skip I see memory spiking but then
it goes back down.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Ok it runs now, but still eats memory as I skip tracks in the playlist.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Ok, try again now?
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/savonet/liquidsoap/issues/511#issuecomment-410722468--
Check
Ok I manually installed the package with ```opam pin add gstreamer
``` and reinstalled LS and everything.
Now LS uses 400MB memory and the threads are using almost no CPU. Seems your
changes killed gstreamer intirely :(
--
You are receiving this because you are subscribed to this thread.
So I tried an ```opam reinstall gstreamer``` (and also ```uninstall
gstreamer``` followed by ``install```), and how I can test is that on the
telnet interface I run ```output(dot)gstreamer.skip``` and I still see the
memory use increase steadily.
Maybe you have to up the version so opam picks
Ah, you didn't change the version number. Not sure if opam is installing the
new ocaml-gstreamer now ..
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Hey,
Could you try with the latest `ocaml-gstreamer`? I've made some changes that
could very well solve this issue..
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
So was this at all useful @toots ?
Just let me know if I can do anything else.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Thanks. This bug has been eluding us for a while, unfortunately.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
I have the feeling I'm experiencing the same issue.
On startup my LS instance uses about ~1.3GB memory but this steadily climbs
until oomkiller comes by to shut it down. Will explore some profiling with
valgrind in a bit.
--
You are receiving this because you are subscribed to this thread.
No. I still don't like this bug. Will have another look at it shortly.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
75 matches
Mail list logo
