Gelmiş geçmiş en büyük porno sitemiz olan 2pe de her zaman en kaliteli pornoları sunmayı hedefledik. Diğer video sitemiz olan vuam da ise hd porno ağırlıklı çalışmalara başladık.

  1. #41
    Ext JS Premium Member westy's Avatar
    Join Date
    Feb 2009
    Location
    Bath, UK
    Posts
    835
    Vote Rating
    38
    westy is a jewel in the rough westy is a jewel in the rough westy is a jewel in the rough

      0  

    Default


    We've seen this too. Best we can hope for is that Mozilla fix it asap I'd say.

    Luckily for us, in a sense, most of our users are on old IEs!
    Never thought I'd ever say that!
    Product Architect
    Altus Ltd.

  2. #42
    Sencha User
    Join Date
    Jun 2012
    Posts
    6
    Vote Rating
    3
    pauld@sitescout.com is on a distinguished road

      1  

    Default


    I did the following and ensure it came right at the top of all my code:

    Code:
    // FIREFOX 18 ION BUG FIX
    Ext.onReady(function(){
        if (Ext.firefoxVersion >= 18) {
            var callOverrideParent = function () {
                var method = callOverrideParent.caller.caller; // skip callParent (our caller)
                try{}catch(e){}   // FF 18 fix
                return method.$owner.prototype[method.$name].apply(this, arguments);
            };
            Ext.override = function (target, overrides) {
                if (target.$isClass) {
                    target.override(overrides);
                } else if (typeof target == 'function') {
                    Ext.apply(target.prototype, overrides);
                } else {
                    var owner = target.self, name, value;
    
                    if (owner && owner.$isClass) { // if (instance of Ext.define'd class)
                        for (name in overrides) {
                            if (overrides.hasOwnProperty(name)) {
                                value = overrides[name];
                                if (typeof value == 'function') {
                                    value.$name = name; value.$owner = owner;
                                    value.$previous = target.hasOwnProperty(name) ? target[name] : callOverrideParent;
                                }
                                target[name] = value;
                            }
                        }
                    } else {
                        Ext.apply(target, overrides);
                    }
                }
    
                return target;
            };
    
            var noArgs = [];
            Ext.override(Ext.Base, {
                callParent: function(args) {
                    var method, superMethod = (method = this.callParent.caller) && (method.$previous ||
                                ((method = method.$owner ? method : method.caller) &&
                                        method.$owner.superclass[method.$name]));
    
                    try {} catch (e) {}    // Firefox 18 fix
    
                    return superMethod.apply(this, args || noArgs);
                },
    
                callSuper: function(args) {
                    var method, superMethod = (method = this.callSuper.caller) &&
                            ((method = method.$owner ? method : method.caller) &&
                                method.$owner.superclass[method.$name]);
    
                    try {} catch (e) {}    // Firefox 18 fix
    
                    return superMethod.apply(this, args || noArgs);
                },
    
                statics: function() {
                    var self = this.self, method = this.statics.caller;
                    try {} catch (e) {}    // Firefox 18 fix
                    if (!method) return self;
    
                    return method.$owner;
                }
    
            });
    
            Ext.override(Ext.Error, {
                raise: function(err) {
                    err = err || {};
                    if (Ext.isString(err)) {
                        err = { msg: err };
                    }
    
                    var msg, method = this.raise.caller;
                    try {} catch (e) {}    // Firefox 18 fix
    
                    if (method) {
                        if (method.$name) {
                            err.sourceMethod = method.$name;
                        }
                        if (method.$owner) {
                            err.sourceClass = method.$owner.$className;
                        }
                    }
    
                    if (Ext.Error.handle(err) !== true) {
                        msg = Ext.Error.prototype.toString.call(err);
    
                        Ext.log({
                            msg: msg,
                            level: 'error',
                            dump: err,
                            stack: true
                        });
    
                        throw new Ext.Error(err);
                    }
                }
            });
        }
    });

  3. #43
    Sencha User
    Join Date
    Mar 2011
    Posts
    22
    Vote Rating
    0
    Aurélien Warnon is on a distinguished road

      0  

    Default


    That workaround still gives me the "too much recursion" error.

    Has anyone found a temporary fix that would allow our users to continue using FF while Mozilla is working on the issue ?

  4. #44
    Sencha User
    Join Date
    Nov 2011
    Posts
    11
    Vote Rating
    0
    pzs1 is on a distinguished road

      0  

    Default


    Did you try patching the libraries directly? (comment #21 and #29)

  5. #45
    Sencha User
    Join Date
    Sep 2010
    Posts
    3
    Vote Rating
    0
    matc1 is on a distinguished road

      0  

    Default


    Hello, this workaround solved problem to me too. Thank's a lot With firefox 18

  6. #46
    Sencha User
    Join Date
    Jan 2009
    Location
    Germany
    Posts
    8
    Vote Rating
    5
    Tyler___Durden is on a distinguished road

      0  

    Default


    Quote Originally Posted by Aurélien Warnon View Post
    That workaround still gives me the "too much recursion" error.

    Has anyone found a temporary fix that would allow our users to continue using FF while Mozilla is working on the issue ?
    Can you post a Stacktrace of the recursion?

  7. #47
    Sencha User
    Join Date
    Jun 2012
    Posts
    6
    Vote Rating
    3
    pauld@sitescout.com is on a distinguished road

      1  

    Default


    Interesting. We've been getting "too much recursion" errors on the dynamic loading version for a while. Eventually I gave up trying to fix it all the time and created a static file to load all the project files for development (besides, it's annoying to wait for everything to load). When I "compile" the project using Sencha's tools on the broken dynamic version, the compiled version works fine.

  8. #48
    Ext JS Premium Member tvanzoelen's Avatar
    Join Date
    Apr 2008
    Location
    Groningen - Netherlands
    Posts
    1,111
    Vote Rating
    30
    tvanzoelen has a spectacular aura about tvanzoelen has a spectacular aura about tvanzoelen has a spectacular aura about

      0  

    Default


    Maybe then it has something to do with dynamic loading. I don't use it, I have all js loaded in one single file. Today with the patch no calls with firefoxproblems and I should have heard if there were any.

  9. #49
    Sencha User
    Join Date
    Jan 2009
    Location
    Germany
    Posts
    8
    Vote Rating
    5
    Tyler___Durden is on a distinguished road

      0  

    Default


    Quote Originally Posted by pauld@sitescout.com View Post
    Interesting. We've been getting "too much recursion" errors on the dynamic loading version for a while. Eventually I gave up trying to fix it all the time and created a static file to load all the project files for development (besides, it's annoying to wait for everything to load). When I "compile" the project using Sencha's tools on the broken dynamic version, the compiled version works fine.
    Good hint, maybe that's an explenation, we're also not using the autoload mechanism....

  10. #50
    Ext Premium Member Jan (HL)'s Avatar
    Join Date
    Aug 2010
    Location
    Germany
    Posts
    111
    Vote Rating
    9
    Jan (HL) will become famous soon enough

      0  

    Default


    Quote Originally Posted by westy View Post
    We've seen this too. Best we can hope for is that Mozilla fix it asap I'd say.

    Luckily for us, in a sense, most of our users are on old IEs!
    Never thought I'd ever say that!
    Patch landed in the release branch last night. Now we are waiting for the next release.

    No insider information, I'm just observing the issue on Mozilla's Bugzilla.