Wiretap (Read Only)
cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

setting numFrames to 0 kills wiretap daemon

3 REPLIES 3
Reply
Message 1 of 4
derrick
522 Views, 3 Replies

setting numFrames to 0 kills wiretap daemon

It looks like the wiretap server is not properly validating input: due to a bug, my code would occasionally try to set the number of frames of a newly created clip to 0. That causes the wiretap daemon to crash with the message:
ifffsWiretapServer: /vobs/develop/src/libMedia/vmedia/videoMedia.C:113: VideoFrame VideoMedia::operator[](int) const: Assertion `frameIdx >= 0 && frameIdx < getNbFrames()' failed.
/usr/discreet/sw/sw_wiretapd: line 38: 31567 Aborted $server_prog $*
3 REPLIES 3
Message 2 of 4
Anonymous
in reply to: derrick

Thanks. We'll validate and get on it right away.
Message 3 of 4
julik_tar
in reply to: derrick

I can confirm (at least with wiretapd on flame 9.5.13), we had to insert a special case for that into our Ruby bindings to avoid killing the server.
Message 4 of 4
labuted
in reply to: derrick

We managed to replicate in house. A fix is on the way for the WT server. It won't make it in for v2007 service pack though.

Thanks for flagging it,

Dan

Can't find what you're looking for? Ask the community or share your knowledge.

Post to forums  

Autodesk Design & Make Report