Im not able to do any work around but halt this project until the
Youtube Chromeless API is updated with the necessary fix.
Can I suggest your Player Team guys take a look at the new
"Netstream.dispose" introduced in Flash Player 11 - see below.
I hope this will solve the issue.
Thanks
Shiraz
NetStream.dispose() — Similar to NetStream.close() except that it also
clears up the last frame held up by NetStream to be displayed on the
Video object. Use this instead of NetStream.close() if the NetStream
is to be re-used for other streams later. It enforces garbage
collection of the video frame and related decompressor objects. The
video object will display a blank frame after the use of this method.
DisplayObjectContainer.removeChildren and MovieClip.isPlaying —
DisplayObjectContainer now implements a removeChildren API allowing
developers to quickly remove all of a container's children using a
single API call. A new MovieClip.isPlaying property returns the
MovieClip's current playing state
On Dec 5, 9:19 pm, Jeffrey Posnick <je...@google.com> wrote:
> Hello Shiraz,
>
> I'm sorry, there aren't any specific fixes that are scheduled to go
> out in the near term. I'd urge you to continue with whatever
> workarounds you've been able to implement in the meantime.
>
> Cheers,
> -Jeff Posnick, YouTube API Team
> groups.google.com/group/youtube-api-gdata | apiblog.youtube.com |
> @YouTubeDev
>
> On Dec 1, 1:23 pm, shirazmexico <shirazmex...@gmail.com> wrote:
>
>
>
>
>
>
>
> > Hi Jeff..
>
> > Im desparate to get this fix...
>
> > according to JJ on 7th Nov :
>
> > "Unfortunately, I don't have anything to share. I added myself to the
> > bug
> > with a note to update this thread and cc you when the fix goes live.
> > In
> > the meantime, I think the best you can do is to check every 5 days and
> > send
> > me email if it hasn't been fixed within 15 days."
>
> > Can you please check with the Player Team and see if there are any
> > further developments to fix the memory leaks and are due to be
> > realeased soon?
>
> > Thanks
> > Shiraz
>
> > On Nov 21, 9:08 pm, Jeffrey Posnick <je...@google.com> wrote:
>
> > > Hello Shiraz,
>
> > > I'm sorry, there are no additional updates at this time. The Players
> > > team has an ongoing goal of reducing/eliminating any sources of leaked
> > > memory that they're aware of, but nothing new has been pushed out
> > > since the last round of updates went out that JJ mentioned.
>
> > > Cheers,
> > > -Jeff Posnick, YouTube API Team
> > > groups.google.com/group/youtube-api-gdata | apiblog.youtube.com |
> > > @YouTubeDev
>
> > > On Nov 18, 1:17 pm, shirazmexico <shirazmex...@gmail.com> wrote:
>
> > > > Hi
>
> > > > Any update on this.. we are desparate to get this fixed asap.
> > > > We notice there are still memory leaks, the commit size keeps growing,
> > > > running for a couple of hours, could this be the cause...?
>
> > > > Thanks
> > > > Shiraz
>
> > > > On Nov 12, 8:07 pm, shiraz ahmed <shirazmex...@hotmail.com> wrote:
>
> > > > > Thanks for the update.. tested the app but still have the issues. Please let me know when the next fixes are completed. Kind RegardsShiraz
> > > > > > Date: Thu, 10 Nov 2011 13:09:21 -0800
>
> > > > > > Subject: [YouTube-API] Re: Youtube Chromeless PlayerHangsFreezes
> > > > > > From: jji...@google.com
> > > > > > To: youtube-api-gdata@googlegroups.com
>
> > > > > > There has been some progress on this bug. Some fixes went live.
> > > > > > However, there is more work to be done. That's all I have for now.
>
> > > > > > Best Regards,
> > > > > > -jj
>
> > > > > > On Nov 7, 11:06 am, Shannon -jj Behrens <jji...@google.com> wrote:
> > > > > > > > Thanks for the reply. How will I know if and when the internal fix has
> > > > > > > > gone live?
> > > > > > > > Is there any Internal Bug ID and website I can view to see the progress of
> > > > > > > > these fixes?
>
> > > > > > > Unfortunately, I don't have anything to share. I added myself to the bug
> > > > > > > with a note to update this thread and cc you when the fix goes live. In
> > > > > > > the meantime, I think the best you can do is to check every 5 days and send
> > > > > > > me email if it hasn't been fixed within 15 days.
>
> > > > > > > "Try writing a bit of JavaScript that checks every 30 seconds that the AS3
>
> > > > > > > > player is alive and well"
> > > > > > > > What should I be checking for exactly in my watchdog app, can you provide
> > > > > > > > any sample etc ?
>
> > > > > > > Unfortunately, I don't have any code since I haven't tried this, but you
> > > > > > > may be able to write some JavaScript that does the following:
>
> > > > > > > window.aboutToCheck = false;
> > > > > > > Use setInterval to call a function every 30 seconds.
> > > > > > > In the watchdog function that gets called every 30 seconds:
> > > > > > > if (window.aboutToCheck) {
> > > > > > > // A previous check failed. Reload the page.
> > > > > > > }
> > > > > > > window.aboutToCheck = true;
> > > > > > > Wrap the following in a try/except block:
> > > > > > > Make a call to the player API to see if it's responding.
> > > > > > > If the player API is working:
> > > > > > > Do some sanity check such as checking that the player has
> > > > > > > progressed since last time if the status says it's playing.
> > > > > > > If there are any problems, reload the page.
> > > > > > > window.aboutToCheck = false;
>
> > > > > > > I hope that's helpful. Sorry you have to do this, but it's the best I can
> > > > > > > offer until the bug is fixed.
>
> > > > > > > -jj
>
> > > > > > > > From: jji...@google.com
> > > > > > > > Date: Mon, 7 Nov 2011 09:30:28 -0800
> > > > > > > > Subject: Re: [YouTube-API] Re: Youtube Chromeless PlayerHangsFreezes
> > > > > > > > To: youtube-api-gdata@googlegroups.com
>
> > > > > > > > Hi Shiraz,
>
> > > > > > > > I tracked down the internal bug that Jeffrey was referring to.
> > > > > > > > Unfortunately, the fix has not gone live yet. Hopefully, the fix will go
> > > > > > > > live soon, and it will fix your problem.
>
> > > > > > > > In the meantime, have you thought about writing a JavaScript watchdog?
> > > > > > > > Try writing a bit of JavaScript that checks every 30 seconds that the AS3
> > > > > > > > player is alive and well. If it isn't, reload the page.
>
> > > > > > > > I'm very sorry for the inconvenience, but that's the best I can offer at
> > > > > > > > this point.
>
> > > > > > > > -jj
>
> > > > > > > > On Thu, Nov 3, 2011 at 9:49 AM, shirazmex...@hotmail.com <
> > > > > > > > shirazmex...@hotmail.com> wrote:
>
> > > > > > > > Hi Jeff
>
> > > > > > > > Ive just tested the above youtube-chromeless1.rar swf file using the
> > > > > > > > Flash Standalone Player today and noticed that we still seem to have
> > > > > > > > the same issue, i.e. the Loop stops and crashes. Has the Youtube
> > > > > > > > update been completed?
> > > > > > > > Am I suppose to make any changes in my code to make it work with the
> > > > > > > > new fixes you mentioned?
> > > > > > > > If so can you please ask the engineer to look at this and let me know
> > > > > > > > what needs to be done.
>
> > > > > > > > Thanks
> > > > > > > > Shiraz
>
> > > > > > > > On Oct 26, 6:06 pm, Jeffrey Posnick <je...@google.com> wrote:
> > > > > > > > > Hello Shiraz,
>
> > > > > > > > > The team that's been investigating memory leaks in monetized
> > > > > > > > > playbacks just submitted a bug fix that they believe will close a few
> > > > > > > > > of those leaks. They aren't positive that it will resolve what you're
> > > > > > > > > seeing, but it is possible. That fix will go live a week from today,
> > > > > > > > > next Wednesday.
>
> > > > > > > > > Cheers,
> > > > > > > > > -Jeff Posnick, YouTube API Team
> > > > > > > > > groups.google.com/group/youtube-api-gdata | apiblog.youtube.com |
> > > > > > > > > @YouTubeDev
>
> > > > > > > > > On Oct 26, 9:55 am, "shirazmex...@hotmail.com"
>
> > > > > > > > > <shirazmex...@hotmail.com> wrote:
> > > > > > > > > > Hi Jeff,
>
> > > > > > > > > > Thanks for the update.
>
> > > > > > > > > > Unfortunately the suggestion you made to periodically purge the player
> > > > > > > > > > and re-initialise will not solve
> > > > > > > > > > the problem as the crash we experience can happen at any time, i.e.
> > > > > > > > > > within minutes of start up of the app or after some hours of play.
> > > > > > > > > > Please test the FLA provided in my original post above.
>
> > > > > > > > > > We would really need your team to fix this bug asap.
> > > > > > > > > > Will you please update me as soon as you can. Im hoping this can be
> > > > > > > > > > fixed within the next few weeks.
>
> > > > > > > > > > Thanks
> > > > > > > > > > Shiraz
>
> > > > > > > > > > On Oct 21, 10:39 pm, Jeffrey Posnick <je...@google.com> wrote:
>
> > > > > > > > > > > Hello Shiraz,
>
> > > > > > > > > > > I'm afraid that I don't have great news for you. The bug has been
> > > > > > > > > > > shuffling around internally, and has ended up being marked as a
> > > > > > > > > > > duplicate of some known issues involving memory leaks with monetized
> > > > > > > > > > > playbacks. That does not mean that the issue is going to be
> > > > > > > > forgotten,
> > > > > > > > > > > but at the same time the team that's been responsible for
> > > > > > > > > > > investigating the previous leaks can't provide any timeline for when
> > > > > > > > > > > they will be resolved.
>
> > > > > > > > > > > I hope it's possible for you to work around this issue by
> > > > > > > > > > > periodically purging the existing player and reinitializing it, as I
> > > > > > > > > > > believe you suggested you were doing. While I know your use case is
> > > > > > > > to
> > > > > > > > > > > play videos back continuously for hours in an uninterrupted sequence,
> > > > > > > > > > > hopefully a pause to perform that won't severely distract from the
> > > > > > > > > > > playback experience.
>
> > > > > > > > > > > Cheers,
> > > > > > > > > > > -Jeff Posnick, YouTube API Team
> > > > > > > > > > > groups.google.com/group/youtube-api-gdata | apiblog.youtube.com |
> > > > > > > > > > > @YouTubeDev
>
> > > > > > > > > > > On Oct 19, 8:46 pm, "shirazmex...@hotmail.com"
>
> > > > > > > > > > > <shirazmex...@hotmail.com> wrote:
> > > > > > > > > > > > Hi Jeff,
>
> > > > > > > > > > > > Its been a month since I reported this Bug and was hoping someone
> > > > > > > > in
> > > > > > > > > > > > the engineer team would have found and fixed this bug by now.
> > > > > > > > > > > > Can you please contact them and let me know.. Ive got an urgent
> > > > > > > > > > > > project to complete and not sure why its taking so long.
> > > > > > > > > > > > As far as the additional debugging information.. I have already
> > > > > > > > > > > > provided the FLA so the engineer can replicate exactly what ive
> > > > > > > > sent.
>
> > > > > > > > > > > > Kind Regards
> > > > > > > > > > > > Shiraz
>
> > > > > > > > > > > > On Oct 12, 10:55 pm, Jeffrey Posnick <je...@google.com> wrote:
>
> > > > > > > > > > > > > Hello Shiraz,
>
> > > > > > > > > > > > > I just spoke to the engineer who's volunteered to look into
> > > > > > > > this. He
> > > > > > > > > > > > > didn't have any specific feedback as to what might be causing
>
> ...
>
> read more »
--
You received this message because you are subscribed to the Google Groups "YouTube APIs Developer Forum" group.
To post to this group, send email to youtube-api-gdata@googlegroups.com.
To unsubscribe from this group, send email to youtube-api-gdata+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/youtube-api-gdata?hl=en.
No comments:
Post a Comment