Memory management issue
Seems like there are still memory problems in 0.3.0.3:
SIGABRT ABORT at 0x0000000198843270
Thread : Crashed: com.videocore.network
0 libsystem_kernel.dylib 0x0000000198843270 __pthread_kill + 8
1 libsystem_pthread.dylib 0x00000001988e1228 pthread_kill + 112
2 libsystem_c.dylib 0x00000001987bab18 abort + 112
3 libc++abi.dylib 0x000000019788d418 __cxa_bad_cast
4 libc++abi.dylib 0x00000001978acb74 default_terminate_handler() + 280
5 libobjc.A.dylib 0x00000001980bc3dc objc_terminate() + 156
6 libc++abi.dylib 0x00000001978a9bb4 std::__terminate(void ()()) + 16
7 libc++abi.dylib 0x00000001978a9478 __cxxabiv1::exception_cleanup_func(_Unwind_Reason_Code, Unwind_Exception)
8 libc++.1.dylib 0x0000000197872314 operator new(unsigned long) + 92
9 libc++.1.dylib 0x00000001978753c4 std::__1::basic_string<char, std::__1::char_traits
What is the URI you are using for establishing your connection?
(lldb) po rtmpUrl rtmp://ec2-52-0-32-132.compute-1.amazonaws.com/live
(lldb) po streamKey c9fc2a3c-1976-4b5f-8007-8d387a933081
It does not crash all the time.
This is a bit of a puzzling one right now, I want to verify that this happens on connect, right?
Also you should see in the logs "playPath: [some value] app: [some value]" could you list that for me as well?
playPath: c9fc2a3c-1976-4b5f-8007-8d387a933081, app: liveClientState: 1
Yes, it happened on connect, few seconds after I saw the preview.
playPath: c9fc2a3c-1976-4b5f-8007-8d387a933081, app: liveClientState: 1 ClientState: 2 ClientState: 3 ClientState: 4 ClientState: 5 ClientState: 6 received server window size: 2500000 received peer bandwidth limit: 2500000 type: 2 received ping, sending pong. Request to change incoming chunk size from 128 -> 512 Received invoke pktId: 1 received invoke _result tracked command: connect ClientState: 7 Received invoke pktId: 4 received invoke _result tracked command: createStream ClientState: 8 received ping, sending pong. Received invoke pktId: 0 received invoke onStatus code : NetStream.Publish.Start ClientState: 9
Are there any steps that you are able to follow to reproduce this crash?
No, I don't. I only saw it once actually.
Any update on this issue?
Hey! Probably I fixed this issue #348