Re: [Live-devel] openRTSP segfault
Hi Ross, First, thank you for your response. I updated to the latest version shortly after posting to the list. The command is truncated from the GDB output, I am specifying -d 86400 and -P 1800. I am specifying -d basically with the intent of having cron start the command once a day with a new -F parameter so that I get files prefixed by -MM-DD. I misunderstood the -v option, thank you. My new command is: openRTSP -B 1000 -b 1000 -4 -f 30 -w 1920 -h 1080 -F "2016-09-20" -d 86400 -P 1800 rtsp://192.168.1.10 I will advise if there are any further issues. -Eric ___ live-devel mailing list live-devel@lists.live555.com http://lists.live555.com/mailman/listinfo/live-devel
Re: [Live-devel] openRTSP segfault
> I have started using openRTSP to try and put together a simple network video > recorder for some Grandstream IP cameras that I have. I am consistently > getting segfaults when running on Ubuntu 14.04 with the livemedia-utils > package installed from apt. First, please upgrade to the latest version of the code (the only version that we support). See http://live555.com/liveMedia/faq.html#latest-version (The version of the “LIVE555 Streaming Media” code included in Linux ‘distros’ is often woefully out-of-date.) > Backtrace from the coredump is below. Basically I am passing flags to > openRTSP to run for 24 hours, and write a new file every 30 minutes. However, that’s not what you’re doing, based on the command-line options that you gave: > Core was generated by `/usr/bin/openRTSP -v -c -B 1000 -b 1000 -4 -Q > -f 30 -F 2016-09-20 -d 86’. Note that the “-v” and “-4” options cause output to go to ‘stdout’ (and thus the "-F ” option is ignored). Also, the “-d 86” option causes the program to read the stream for only 86 seconds each time (and then the “-c” option causes it to reopen the stream again afterwards). Also, because you’re using the “-4” option (to generate a “.mp4"-format file), you should also include not just the "-f ” option, but also the “-w ” and "-h ” option; see http://live555.com/openRTSP/#quicktime If you want to generate multiple output files - once every 30 minutes, then way to do this is with the option -P 1800 and omit the “-c” and “-d” options. However, I suggest that you first make sure that you can generate a single playable video file, by running openRTSP -4 -B 1000 -b 1000 -f 30 -w foo -h bar -d 30 rtsp://mumble > test.mp4 (Replace “foo”, “bar”, and “mumble” with actual width, height, and URL.) This will (after 30 seconds of streaming) generate a file “test.mp4”. Make sure that it’s playable. Then, and only then, should you run openRTSP -4 -B 1000 -b 1000 -f 30 -w foo -h bar -P 1800 rtsp://mumble which will generate an output file every 30 minutes. Ross Finlayson Live Networks, Inc. http://www.live555.com/ ___ live-devel mailing list live-devel@lists.live555.com http://lists.live555.com/mailman/listinfo/live-devel
Re: [Live-devel] openRTSP segfault
I've downloaded and compiled the latest tgz and so far i've gotten 2 files written with no segfault, so we will see. On 09/20/2016 12:34 PM, Eric Tamme wrote: Hello all, I have started using openRTSP to try and put together a simple network video recorder for some Grandstream IP cameras that I have. I am consistently getting segfaults when running on Ubuntu 14.04 with the livemedia-utils package installed from apt. Backtrace from the coredump is below. Basically I am passing flags to openRTSP to run for 24 hours, and write a new file every 30 minutes. I only ever get a single file, and I believe it is segfaulting around the time it writes the new file. Any help on further debugging/solving the problem would be appreciated. -Eric Core was generated by `/usr/bin/openRTSP -v -c -B 1000 -b 1000 -4 -Q -f 30 -F 2016-09-20 -d 86'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x7f4345b14800 in FramedSource::stopGettingFrames() () from /usr/lib/x86_64-linux-gnu/libliveMedia.so.23 (gdb) bt #0 0x7f4345b14800 in FramedSource::stopGettingFrames() () from /usr/lib/x86_64-linux-gnu/libliveMedia.so.23 #1 0x7f4345b575cc in QuickTimeFileSink::~QuickTimeFileSink() () from /usr/lib/x86_64-linux-gnu/libliveMedia.so.23 #2 0x7f4345b57659 in QuickTimeFileSink::~QuickTimeFileSink() () from /usr/lib/x86_64-linux-gnu/libliveMedia.so.23 #3 0x004030c5 in ?? () #4 0x004046db in ?? () #5 0x7f434568551b in AlarmHandler::handleTimeout() () from /usr/lib/x86_64-linux-gnu/libBasicUsageEnvironment.so.0 #6 0x7f4345685e3a in BasicTaskScheduler::SingleStep(unsigned int) () from /usr/lib/x86_64-linux-gnu/libBasicUsageEnvironment.so.0 #7 0x7f4345684e8c in BasicTaskScheduler0::doEventLoop(char*) () from /usr/lib/x86_64-linux-gnu/libBasicUsageEnvironment.so.0 #8 0x00402a12 in ?? () #9 0x7f4344bb1f45 in __libc_start_main (main=0x401e80, argc=18, argv=0x7ffd91e1e908, init=, fini=, rtld_fini=, stack_end=0x7ffd91e1e8f8) at libc-start.c:287 #10 0x00402e22 in ?? () ___ live-devel mailing list live-devel@lists.live555.com http://lists.live555.com/mailman/listinfo/live-devel
Re: [Live-devel] openRTSP segfault on max osx
running openRTSP -q -w 704 -h 576 rtsp://192.168.0.101/axis-media/media.amp test.mov and sending kill -HUP sometimes ends with a segfault. This is with live555 2010.06.18 but I didn't see this with 2010.04.09 Aha! You've found a bug in the openRTSP code. We're closing the output file(s) too soon. (This bug turned out to be a problem only with the new RTSPClient implementation, because - in this new implementation - we go to the event loop (potentially handling incoming RTP data) while awaiting the response to the RTSP TEARDOWN command.) Please try the following, which should fix this problem: In testProgs/playCommon.cpp, line 1104, move the statement closeMediaSinks(); down 5 lines, so that it now takes place after Medium::close(session); -- Ross Finlayson Live Networks, Inc. http://www.live555.com/ ___ live-devel mailing list live-devel@lists.live555.com http://lists.live555.com/mailman/listinfo/live-devel
Re: [Live-devel] openRTSP segfault on max osx
Please try the following, which should fix this problem: In testProgs/playCommon.cpp, line 1104, move the statement closeMediaSinks(); down 5 lines, so that it now takes place after Medium::close(session); It turns out that I didn't have this quite right. The correct sequence of statements - starting at line 1104 - should be: tearDownStreams(); closeMediaSinks(); Medium::close(session); I have now installed a new version (2010.06.22) of the code that fixes this bug (as well as Sebastien Escudier's latest RTSPClient bug). -- Ross Finlayson Live Networks, Inc. http://www.live555.com/ ___ live-devel mailing list live-devel@lists.live555.com http://lists.live555.com/mailman/listinfo/live-devel
Re: [Live-devel] openRTSP segfault on max osx
22 jun 2010 kl. 11.26 skrev Ross Finlayson: Please try the following, which should fix this problem: In testProgs/playCommon.cpp, line 1104, move the statement closeMediaSinks(); down 5 lines, so that it now takes place after Medium::close(session); It turns out that I didn't have this quite right. The correct sequence of statements - starting at line 1104 - should be: tearDownStreams(); closeMediaSinks(); Medium::close(session); I have now installed a new version (2010.06.22) of the code that fixes this bug (as well as Sebastien Escudier's latest RTSPClient bug). -- Ross Finlayson Live Networks, Inc. http://www.live555.com/ ___ live-devel mailing list live-devel@lists.live555.com http://lists.live555.com/mailman/listinfo/live-devel Works perfectly. Thanks for your quick fix and effort, it's great software. Kenneth ___ live-devel mailing list live-devel@lists.live555.com http://lists.live555.com/mailman/listinfo/live-devel
