Skip to main content
Participant
November 8, 2016
Question

Range Error on flashplayer in firefox

  • November 8, 2016
  • 1 reply
  • 275 views

hi,

we are developing a virtual camera as a directshow source filter. The Vcam works well with flashplayer in google chrome. But the flash player in firefox repeatedly instantiate the vcam and throws the error with the debug version of flash.

RangeError: Error #2006: The supplied index is out of bounds. at flash.media::Video/ctor().

No idea of what goes wrong. I have installed the latested version of flash (23.0.0.205).

Please give me some idea on what is wrong.

Thankyou.

    This topic has been closed for replies.

    1 reply

    jeromiec83223024
    Inspiring
    November 9, 2016

    It's unclear.  The underlying C++ constructor for the Video object is expecting a parameter value in a defined range, and it's getting something outside of that (most likely null, if I had to guess).  We see that the value is inappropriate and throw an error.

    The most likely outcome is that we're getting an invalid value from Firefox, and either what you're trying to do isn't going to work in their architecture, or you'd need a bugfix from them. 

    If this is 32-bit Firefox, does disabling protected mode help?

    Adobe Flash protected mode in Firefox | Firefox Help

    Do you have the same problem in 64-bit Firefox?

    Participant
    November 11, 2016

    Hi jerotmiec,

    Thanks for your reply.

    I tried disabling the protected mode as said in the link. But its not working.

    The problem is simple. I have a source filter which act as virtual camera and send custom video as source from my filter.

    But after the media type negotiations( getmediatype and checkmediatype) from directshow the error is thrown.

    jeromiec83223024
    Inspiring
    November 11, 2016

    Yeah, I was hoping it was just something that we were blocking with the sandbox.  This isn't really a use-case that we support, so there's no public documentation.  We're basically just enumerating the available cameras that the browser exposes to us. 

    Is it possible that your virtual camera is too big?  Have you experimented with small camera sizes ( < 640x480) to see if we throw the range error there?

    My guess is that we'd need to debug this to figure out what exactly is going on.  If you already have an enterprise support agreement with Adobe, it might fall under the scope of that support agreement.  Your support representative should be able to help navigate that.  If not, I'd be happy to refer you to our business development folks to explore what option makes the most sense in terms of getting direct engineering support for your new product.

    Thanks!