[jitsi-dev] Libjitsi bug : Can't create RTPTranslator and setConnector throw an exception


#1

Hi,

I tried to used the latest version of libjitsi with jitsi-hammer but I encounter some bugs, but I don't know if it's me or libjitsi :
-The call to MediaServiceImpl.createRTPTranslator() never returns, it seems like an Exception is thrown but the thread doesn't log it.

-If I comment out the creation and set of the RTPTranslator (I'm not even sure I need it but hey, it can't hurt), the hammer can continue, but it stop again when I try to set the connector (DefaultStreamConnector) to the MediaStream. I've tracked down the error to MediaStreamImpl.createTransformEngineChain(), the line 410 with the instruction "statisticsEngine = new StatisticsEngine(this);". Again, it seems like the JVM throw an Exception but does not log it.

Thomas Kuntz.


#2

Just a quick follow up, I've track down the problem when I set the connector of the MediaStream, to the commit b33e45dbff9184bcf67b9cac691e994786c57ef5 : after this commit (included), setConnector doesn't work for me.

For the createRTPTranslator error, I've track this bug down to the commit af749fb7d0581972f169d9da043494c841f02830 (but it might also be the 2 commits before dd4b2a589ce0dcac8259704c66010deeae8e8db9 and d90c77dc91fab8295436d12571d873caabe1d418 : I can't be sure because I can't compile libjitsi at these commits).

I don't know If that helps you.

Thomas.

Le 19/07/2014 14:15, Thomas Kuntz a �crit :

···

Hi,

I tried to used the latest version of libjitsi with jitsi-hammer but I encounter some bugs, but I don't know if it's me
or libjitsi :
-The call to MediaServiceImpl.createRTPTranslator() never returns, it seems like an Exception is thrown but the thread
doesn't log it.

-If I comment out the creation and set of the RTPTranslator (I'm not even sure I need it but hey, it can't hurt), the
hammer can continue, but it stop again when I try to set the connector (DefaultStreamConnector) to the MediaStream. I've
tracked down the error to MediaStreamImpl.createTransformEngineChain(), the line 410 with the instruction
"statisticsEngine = new StatisticsEngine(this);". Again, it seems like the JVM throw an Exception but does not log it.

Thomas Kuntz.


#3

Hi,

I tried to used the latest version of libjitsi with jitsi-hammer but
I encounter some bugs, but I don't know if it's me or libjitsi :
-The call to MediaServiceImpl.createRTPTranslator() never returns,
it seems like an Exception is thrown but the thread doesn't log it.

Are you sure it's the MediaServiceImpl.createRTPTranslator() method that
crashes? I'm not seeing anything suspicious in there.

-If I comment out the creation and set of the RTPTranslator (I'm not
even sure I need it but hey, it can't hurt), the hammer can
continue, but it stop again when I try to set the connector
(DefaultStreamConnector) to the MediaStream. I've tracked down the
error to MediaStreamImpl.createTransformEngineChain(), the line 410
with the instruction "statisticsEngine = new
StatisticsEngine(this);". Again, it seems like the JVM throw an
Exception but does not log it.

Can you try putting that line inside a try/catch statement and log the
exception inside the catch part?

···

On Sat, Jul 19, 2014 at 02:15:52PM +0200, Thomas Kuntz wrote:

Thomas Kuntz.

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev


#4

Just a quick follow up, I've track down the problem when I set the
connector of the MediaStream, to the commit
b33e45dbff9184bcf67b9cac691e994786c57ef5 : after this commit
(included), setConnector doesn't work for me.

For the createRTPTranslator error, I've track this bug down to the
commit af749fb7d0581972f169d9da043494c841f02830 (but it might also
be the 2 commits before dd4b2a589ce0dcac8259704c66010deeae8e8db9 and
d90c77dc91fab8295436d12571d873caabe1d418 : I can't be sure because I
can't compile libjitsi at these commits).

You can't compile libjitsi at these commits probably because you need a
newer lib/fmj.jar. I didn't update fmj.jar because I hadn't pushed my
changes to FMJ upstream yet at that point.

A work-around would be to keep the fmj.jar from a more recent commit.

···

On Sat, Jul 19, 2014 at 03:01:23PM +0200, Thomas Kuntz wrote:

I don't know If that helps you.

Thomas.

Le 19/07/2014 14:15, Thomas Kuntz a �crit :

Hi,

I tried to used the latest version of libjitsi with jitsi-hammer but I encounter some bugs, but I don't know if it's me
or libjitsi :
-The call to MediaServiceImpl.createRTPTranslator() never returns, it seems like an Exception is thrown but the thread
doesn't log it.

-If I comment out the creation and set of the RTPTranslator (I'm not even sure I need it but hey, it can't hurt), the
hammer can continue, but it stop again when I try to set the connector (DefaultStreamConnector) to the MediaStream. I've
tracked down the error to MediaStreamImpl.createTransformEngineChain(), the line 410 with the instruction
"statisticsEngine = new StatisticsEngine(this);". Again, it seems like the JVM throw an Exception but does not log it.

Thomas Kuntz.

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev


#5

Mmhh well that's embarrassing.
It works now, I just forgot to update the fmj jar of jitsi-hammer...

Sorry for the false alarm...

Thanks for the help !

Thomas Kuntz.

Le 19/07/2014 22:21, George Politis a �crit :

···

On Sat, Jul 19, 2014 at 03:01:23PM +0200, Thomas Kuntz wrote:

Just a quick follow up, I've track down the problem when I set the
connector of the MediaStream, to the commit
b33e45dbff9184bcf67b9cac691e994786c57ef5 : after this commit
(included), setConnector doesn't work for me.

For the createRTPTranslator error, I've track this bug down to the
commit af749fb7d0581972f169d9da043494c841f02830 (but it might also
be the 2 commits before dd4b2a589ce0dcac8259704c66010deeae8e8db9 and
d90c77dc91fab8295436d12571d873caabe1d418 : I can't be sure because I
can't compile libjitsi at these commits).

You can't compile libjitsi at these commits probably because you need a
newer lib/fmj.jar. I didn't update fmj.jar because I hadn't pushed my
changes to FMJ upstream yet at that point.

A work-around would be to keep the fmj.jar from a more recent commit.

I don't know If that helps you.

Thomas.

Le 19/07/2014 14:15, Thomas Kuntz a �crit :

Hi,

I tried to used the latest version of libjitsi with jitsi-hammer but I encounter some bugs, but I don't know if it's me
or libjitsi :
-The call to MediaServiceImpl.createRTPTranslator() never returns, it seems like an Exception is thrown but the thread
doesn't log it.

-If I comment out the creation and set of the RTPTranslator (I'm not even sure I need it but hey, it can't hurt), the
hammer can continue, but it stop again when I try to set the connector (DefaultStreamConnector) to the MediaStream. I've
tracked down the error to MediaStreamImpl.createTransformEngineChain(), the line 410 with the instruction
"statisticsEngine = new StatisticsEngine(this);". Again, it seems like the JVM throw an Exception but does not log it.

Thomas Kuntz.

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev


#6

Mmhh well that's embarrassing.
It works now

Good to know!

···

On dim., juil. 20, 2014 at 03:17:19 +0200, Thomas Kuntz wrote:

I just forgot to update the fmj jar of jitsi-hammer...

Sorry for the false alarm...

Thanks for the help !

Thomas Kuntz.

Le 19/07/2014 22:21, George Politis a �crit :

On Sat, Jul 19, 2014 at 03:01:23PM +0200, Thomas Kuntz wrote:

Just a quick follow up, I've track down the problem when I set the
connector of the MediaStream, to the commit
b33e45dbff9184bcf67b9cac691e994786c57ef5 : after this commit
(included), setConnector doesn't work for me.

For the createRTPTranslator error, I've track this bug down to the
commit af749fb7d0581972f169d9da043494c841f02830 (but it might also
be the 2 commits before dd4b2a589ce0dcac8259704c66010deeae8e8db9 and
d90c77dc91fab8295436d12571d873caabe1d418 : I can't be sure because I
can't compile libjitsi at these commits).

You can't compile libjitsi at these commits probably because you need a
newer lib/fmj.jar. I didn't update fmj.jar because I hadn't pushed my
changes to FMJ upstream yet at that point.

A work-around would be to keep the fmj.jar from a more recent commit.

I don't know If that helps you.

Thomas.

Le 19/07/2014 14:15, Thomas Kuntz a �crit :

Hi,

I tried to used the latest version of libjitsi with jitsi-hammer but I encounter some bugs, but I don't know if it's me
or libjitsi :
-The call to MediaServiceImpl.createRTPTranslator() never returns, it seems like an Exception is thrown but the thread
doesn't log it.

-If I comment out the creation and set of the RTPTranslator (I'm not even sure I need it but hey, it can't hurt), the
hammer can continue, but it stop again when I try to set the connector (DefaultStreamConnector) to the MediaStream. I've
tracked down the error to MediaStreamImpl.createTransformEngineChain(), the line 410 with the instruction
"statisticsEngine = new StatisticsEngine(this);". Again, it seems like the JVM throw an Exception but does not log it.

Thomas Kuntz.

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev