Hi Ray

It seems your assumption was spot on. Forcing curl to not initialise openssl removed the issue (I know pjsip always starts first so openssl will be initialised by pjsip always).

Just like in the Asterix bug (and probably also okhttp) the issue appears to stem from initialising openssl more than once. Maybe as you say, this will be better in 1.1.0.

Even though I can control the startup process I still feel that I have no idea on if threading can cause issues further down the road. The reproducible problem did go away when removing the double openssl init but I fear that strange threading issues might happen if openssl is shared between the two libs (pjsip+curl).

For now, maybe the safer option is to separate the sip and http functionality into their own dynlibs, each with its own copy of libcrypto and libssl. The .apk size will quite a lot bigger but a part from that it appears to work fine.

Thanks for the help digging into this

Johan

________________________________

Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, puede contener información privilegiada o confidencial y es para uso exclusivo de la persona o entidad de destino. Si no es usted. el destinatario indicado, queda notificado de que la lectura, utilización, divulgación y/o copia sin autorización puede estar prohibida en virtud de la legislación vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma vía y proceda a su destrucción.

The information contained in this transmission is privileged and confidential information intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this transmission in error, do not read it. Please immediately reply to the sender that you have received this communication in error and then delete it.

Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinatário, pode conter informação privilegiada ou confidencial e é para uso exclusivo da pessoa ou entidade de destino. Se não é vossa senhoria o destinatário indicado, fica notificado de que a leitura, utilização, divulgação e/ou cópia sem autorização pode estar proibida em virtude da legislação vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique imediatamente por esta mesma via e proceda a sua destruição

-------------------------------------------------------------------
List admin: https://cool.haxx.se/list/listinfo/curl-library
Etiquette: https://curl.haxx.se/mail/etiquette.html
Received on 2016-04-20