Skip to main content
Chicohuman
Chicohuman
Known Participant
October 26, 2012
Question

Weird issue: application.onDisconnect delayed in Chrome

  • October 26, 2012
  • 2 replies
  • 4089 views

Hi,

I have an application in which we use application.onDisconnect when a user logs out.

In all browsers, we can see in the FMS admin console that the user has indeed been disconnected, except when the user uses Chrome.

It can take minutes before the application.onDisconnect is fired.

Known issue? Any work around?

Thank you

    This topic has been closed for replies.

    2 replies

    T
    Tunyesz_
    Participant
    February 15, 2013

    Any solution for this?

    I think its such a huge problem that i cant use rtmfp on chrome.

    I cant tell my chomre customers "plz disable pepper flash plugin to user our service".

    In this way rtmp is the only solution, right?

    Anyway I'm very glad cos I've spent hours to find the solution in the FMS configuration XMLs, before this post.

    Google its your turn

    Chicohuman
    ChicohumanAuthor
    Known Participant
    February 16, 2013

    Just to follow up in this thread:

    Back then Manish and I exchanged a few emails and he was able to reproduce the issue.
    The bug was reported and let's hope it's being worked on.

    A
    Anonymous
    April 7, 2013

    any news of this bug ?

    I just reproduced it today, april 2013 with last Chrome 26.01.1410.43

    with RTMFP connection. the instance leaves after 10 hours! :-\

    RTMP works well

    I see some NetStream instances leave, but NetConnection stays

    maybe is there any related point with persistent http 1.1 ?

    tried on windows XP SP3

    but it works on MAC os X

    N
    Adobe Employee
    NpComplete
    Adobe Employee
    October 26, 2012

    Can you please check the application log on the server. You must check the log entry time in the log. It may happen chrome is delaying the update of event on flash.

    Chicohuman
    ChicohumanAuthor
    Known Participant
    October 26, 2012

    In fact when using Chrome, the event is always delayed, whereas firefox or IE will immediately fire the event when a user logs out.  I see it live from the Adobe Admin Console - before the event fires on Chrome it will take minutes.

    Chrome's having issues lately, another issue we had was with the camera resolutions - they were at 320x240 and Flash was crashing - we changed it to 320x239 and then it's fine most of the time (saw this fix on another forum, somebody had it too).  Anyway, back to the main issue of this thread

    Thanks for your answer, appreciate it!

    Dany

    Chicohuman
    ChicohumanAuthor
    Known Participant
    October 28, 2012

    Bump. Want to make sure this critical issue gets picked up by Adobe engineers.

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices