[jitsi-dev] WASAPI Exceptions


#1

Hey

I recently see a lot of exceptions coming from WASAPI:

13:34:34.483 Schwerwiegend: [210] util.UtilActivator.uncaughtException().108
An uncaught exception occurred in thread=Thread[pool-14-thread-1,5,main] and
message was: Array index out of range: 3372
java.lang.ArrayIndexOutOfBoundsException: Array index out of range: 3372
  at java.util.Arrays.rangeCheck(Unknown Source)
  at java.util.Arrays.fill(Unknown Source)
  at
org.jitsi.impl.neomedia.jmfext.media.renderer.audio.WASAPIRenderer.runInEven
tHandleCmd(WASAPIRenderer.java:1401)
  at
org.jitsi.impl.neomedia.jmfext.media.renderer.audio.WASAPIRenderer.access$0(
WASAPIRenderer.java:1301)
  at
org.jitsi.impl.neomedia.jmfext.media.renderer.audio.WASAPIRenderer$1.run(WAS
APIRenderer.java:1614)
  at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
  at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown
Source)
  at java.lang.Thread.run(Unknown Source)

13:34:34.594 Warnung: [127]
org.jitsi.impl.neomedia.jmfext.media.renderer.audio.WASAPIRenderer.warn()
Audio endpoint device appears to be malfunctioning:
wasapi:{0.0.0.00000000}.{033983fa-0253-468a-858b-a23cb86392f0}

13:34:34.594 Schwerwiegend: [127]
org.jitsi.impl.neomedia.notify.AudioSystemClipImpl.error() Failed to render
audio stream resources/sounds/hangup.wav

Any input how I can track that down?
Calls still work, as does ringing etc., but e.g. hanging up a call takes
sometimes 10 to 15 seconds.

Ingo


#2

No, doesn't look like something we've seen recently and it isn't clear
exactly when such a thing could occur.

Emil

···

On Mon, Feb 10, 2014 at 1:39 PM, Ingo Bauersachs <ingo@jitsi.org> wrote:

Hey

I recently see a lot of exceptions coming from WASAPI:

13:34:34.483 Schwerwiegend: [210] util.UtilActivator.uncaughtException().108
An uncaught exception occurred in thread=Thread[pool-14-thread-1,5,main] and
message was: Array index out of range: 3372
java.lang.ArrayIndexOutOfBoundsException: Array index out of range: 3372
        at java.util.Arrays.rangeCheck(Unknown Source)
        at java.util.Arrays.fill(Unknown Source)
        at
org.jitsi.impl.neomedia.jmfext.media.renderer.audio.WASAPIRenderer.runInEven
tHandleCmd(WASAPIRenderer.java:1401)
        at
org.jitsi.impl.neomedia.jmfext.media.renderer.audio.WASAPIRenderer.access$0(
WASAPIRenderer.java:1301)
        at
org.jitsi.impl.neomedia.jmfext.media.renderer.audio.WASAPIRenderer$1.run(WAS
APIRenderer.java:1614)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown
Source)
        at java.lang.Thread.run(Unknown Source)

13:34:34.594 Warnung: [127]
org.jitsi.impl.neomedia.jmfext.media.renderer.audio.WASAPIRenderer.warn()
Audio endpoint device appears to be malfunctioning:
wasapi:{0.0.0.00000000}.{033983fa-0253-468a-858b-a23cb86392f0}

13:34:34.594 Schwerwiegend: [127]
org.jitsi.impl.neomedia.notify.AudioSystemClipImpl.error() Failed to render
audio stream resources/sounds/hangup.wav

Any input how I can track that down?
Calls still work, as does ringing etc., but e.g. hanging up a call takes
sometimes 10 to 15 seconds.

Ingo

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

--
https://jitsi.org


#3

Well, I'd try to fix it myself, but I don't know enough about all the WASAPI
handling, but something in the silence-handling is definitely weird:

(in WASAPISystem.java)
//open(){
//numBufferFrames=960
//srcFrameSize=2

...
remainder = new byte[numBufferFrames * srcFrameSize];
//--> remainder.length is 1920
//}

//runInEventHandleCmd(){
numPaddingFrames = 348
numFramesRequested = 960 - 348 = 612

// downsampling using speex from 44100 to 16000
numFramesRequested = 1686

//remainderLength=0
//srcFrameSize=2
toWrite = numFramesRequested * srcFrameSize = 3372

//}

-> Now filling an array outside of its bounds obviously fails...

Any ideas?

Ingo

From: dev-bounces@jitsi.org [mailto:dev-bounces@jitsi.org] On Behalf Of

Emil

Ivov
Sent: Freitag, 14. Februar 2014 10:44
To: Jitsi Developers
Subject: Re: [jitsi-dev] WASAPI Exceptions
No, doesn't look like something we've seen recently and it isn't clear
exactly when such a thing could occur.

Emil

Hey

I recently see a lot of exceptions coming from WASAPI:

13:34:34.483 Schwerwiegend: [210]
util.UtilActivator.uncaughtException().108 An uncaught exception
occurred in thread=Thread[pool-14-thread-1,5,main] and message was:
Array index out of range: 3372
java.lang.ArrayIndexOutOfBoundsException: Array index out of range: 3372
        at java.util.Arrays.rangeCheck(Unknown Source)
        at java.util.Arrays.fill(Unknown Source)
        at
org.jitsi.impl.neomedia.jmfext.media.renderer.audio.WASAPIRenderer.runIn
Even tHandleCmd(WASAPIRenderer.java:1401)
        at
org.jitsi.impl.neomedia.jmfext.media.renderer.audio.WASAPIRenderer.acces
s$0( WASAPIRenderer.java:1301)
        at
org.jitsi.impl.neomedia.jmfext.media.renderer.audio.WASAPIRenderer$1.run
(WAS APIRenderer.java:1614)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown
        Source) at
        java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown
        Source) at java.lang.Thread.run(Unknown Source)
13:34:34.594 Warnung: [127]
org.jitsi.impl.neomedia.jmfext.media.renderer.audio.WASAPIRenderer.warn()
Audio endpoint device appears to be malfunctioning:
wasapi:{0.0.0.00000000}.{033983fa-0253-468a-858b-a23cb86392f0}

13:34:34.594 Schwerwiegend: [127]
org.jitsi.impl.neomedia.notify.AudioSystemClipImpl.error() Failed to

render

···

-----Original Message-----
On Mon, Feb 10, 2014 at 1:39 PM, Ingo Bauersachs <ingo@jitsi.org> wrote:

audio stream resources/sounds/hangup.wav

Any input how I can track that down?
Calls still work, as does ringing etc., but e.g. hanging up a call takes
sometimes 10 to 15 seconds.

Ingo

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


#4

Hello, Ingo!

I saw that you committed changes to WASAPI and I'd like to ask whether
you're looking into the issue or I should try?

Best regards,
Lyubomir


#5

Hey

I saw that you committed changes to WASAPI and I'd like to ask whether
you're looking into the issue or I should try?

I fixed what I could, but the other exceptions are beyond my knowledge, so
I'd be grateful if you could take a look.

Best regards,
Lyubomir

Thanks!
Ingo