Prev: Create Password Protected PDF from byteArrayInputStream
Next: persistence / object backend to file / serialization
From: Richard Maher on 30 Jan 2010 23:54 Hi, Just a bit more info from the FireFox 3 side of things. After some time, with a single Randomator tab and 5 EmpPickers, the Error Console spewed out: - "Too much recursion" at . .mozilla firefox/components/nsPlacesDBFlush.js line 259 and then just reverted to: - "Too much recursion" "Too much recursion" "Too much recursion" before disappearing up it's own bottom Hey, it's probably me but I just can't see the recursion at the moment :-( I'm at pains to use setTimeout() to deliver an unparented, top-level, stack-virginal event (come Asynchronous System Trap) to reset the depth each time; what have I missed? What does nsPlacesDBFlush do at munged-line 259 and could it be a FF bug or just another red-herring pointing to the floundering of the page author? Cheers Richard Maher PS. While Chrome has issues of it's own with Applets this appears not to be one of them. As we speak Chrome with 2 x 5 EmpPicker tabs has been rockin' & rollin for over 3 hours. (Fading's a bit weird/slow though) "Richard Maher" <maher_rj(a)hotspamnotmail.com> wrote in message news:hk2ma6$bdo$1(a)news-01.bur.connect.com.au... > > "rf" <rf(a)z.invalid> wrote in message > news:mGV8n.4470$pv.2108(a)news-server.bigpond.net.au... > > > > "Richard Maher" <maher_rj(a)hotspamnotmail.com> wrote in message > > news:hk04i8$bt$1(a)news-01.bur.connect.com.au... > > > Hi, > > > > > > Does anyone know what might cause the above error to be thrown from a > > > myFun.apply(this,stuf) call? > > > > What above error? > > > > Not sure what newsgroup reader you're using but in everyone I've seen you'll > find a subject line or title for my post that says: - > " func.apply() throws Error -2147467259" > > But if it helps clarify things the error is caught and rethrown in > Tier3Client.js (which was included as a response to my original post) circa > line 188 character 24. The exception "name" was "Error" and the "number" > was -2147467259. All other attributes were unavailable and toString() > revealed [object Error] > > So, in a nutshell, when I try to call (apply) the user's callback routine > IE8/Windows says no but won't say why. I was hoping someone could tell me > some great debugging option that might reveal additional information about > the "Error" or perhaps some buttons/quotas to push that might reval more. > > Please note that this could be a timing/collision thing, as upping the > number of EmpPickers to 5 results in attrition of employees back to zero. > The "good" news is that the rendezvous() function must have been called (and > the JAVA console backs that up) or the browser would hang very quickly so > I'm off to see how far in positionDiv the code gets. > > Stack Limit? > > Maybe each DIV get's displayed the same amount of times before bombing? > > Some recurrsiveness I'm missing? > > Oh well, I guess I was just hoping that "Error -2147467259" wasn't as > generic as it looks and it might have rung a bell with someone. I'd better > roll up the sleaves. . . > > > > > > Regards Richard Maher > >
From: Stefan Weiss on 31 Jan 2010 05:35 On 31/01/10 05:54, Richard Maher wrote: > Just a bit more info from the FireFox 3 side of things. After some time, > with a single Randomator tab and 5 EmpPickers, the Error Console spewed > out: - > > "Too much recursion" at . .mozilla firefox/components/nsPlacesDBFlush.js > line 259 and then just reverted to: - > > "Too much recursion" > "Too much recursion" > "Too much recursion" > > before disappearing up it's own bottom > > Hey, it's probably me but I just can't see the recursion at the moment :-( > I'm at pains to use setTimeout() to deliver an unparented, top-level, > stack-virginal event (come Asynchronous System Trap) to reset the depth each > time; what have I missed? Are you using Firebug? I've seen that error a few times, and always in situations where my code couldn't possibly recurse. Disabling Firebug solved the problem. -- stefan
From: Richard Maher on 31 Jan 2010 06:20 Hi Stefan, "Stefan Weiss" <krewecherl(a)gmail.com> wrote in message news:gsOdnYvsl7xAwfjWnZ2dnUVZ8lydnZ2d(a)giganews.com... > On 31/01/10 05:54, Richard Maher wrote: > > Just a bit more info from the FireFox 3 side of things. After some time, > > with a single Randomator tab and 5 EmpPickers, the Error Console spewed > > out: - > > > > "Too much recursion" at . .mozilla firefox/components/nsPlacesDBFlush.js > > line 259 and then just reverted to: - > > > > "Too much recursion" > > "Too much recursion" > > "Too much recursion" > > > > before disappearing up it's own bottom > > > > Hey, it's probably me but I just can't see the recursion at the moment :-( > > I'm at pains to use setTimeout() to deliver an unparented, top-level, > > stack-virginal event (come Asynchronous System Trap) to reset the depth each > > time; what have I missed? > > Are you using Firebug? I've seen that error a few times, and always in > situations where my code couldn't possibly recurse. Disabling Firebug > solved the problem. Yes, I got it first with Firebug but after turning Firebug off I'm still getting it with FF 3.5.7 :-( (Error console still on though) A further update: - FireFox 2.0.0.4 has absolutely no problem with processing 3 tabs, 5 EmpPickers per tab and a 1 sec fade time after 4 hours. But then FF2 doesn't have the components/nsPlacesDBFlush.js script either. Chrome with the same load is also soldiering on admirably and not missing a beat for about 6 hours! > > > -- > stefan Cheers Richard Maher
From: Richard Maher on 5 Feb 2010 23:35 HI again Stefan, "Stefan Weiss" <krewecherl(a)gmail.com> wrote in message news:gsOdnYvsl7xAwfjWnZ2dnUVZ8lydnZ2d(a)giganews.com... > On 31/01/10 05:54, Richard Maher wrote: > > Just a bit more info from the FireFox 3 side of things. After some time, > > with a single Randomator tab and 5 EmpPickers, the Error Console spewed > > out: - > > > > "Too much recursion" at . .mozilla firefox/components/nsPlacesDBFlush.js > > line 259 and then just reverted to: - > > > > "Too much recursion" > > "Too much recursion" > > "Too much recursion" > > > > before disappearing up it's own bottom > > > > Hey, it's probably me but I just can't see the recursion at the moment :-( > > I'm at pains to use setTimeout() to deliver an unparented, top-level, > > stack-virginal event (come Asynchronous System Trap) to reset the depth each > > time; what have I missed? > > Are you using Firebug? I've seen that error a few times, and always in > situations where my code couldn't possibly recurse. Disabling Firebug > solved the problem. > What have you used to replace console.log(reallyUsefulStuff) when you have had to disable FireBug? > > -- > stefan Cheers Richard Maher
From: Stefan Weiss on 6 Feb 2010 12:49
On 06/02/10 05:35, Richard Maher wrote: > "Stefan Weiss" <krewecherl(a)gmail.com> wrote in message > news:gsOdnYvsl7xAwfjWnZ2dnUVZ8lydnZ2d(a)giganews.com... >> Are you using Firebug? I've seen that error a few times, and always in >> situations where my code couldn't possibly recurse. Disabling Firebug >> solved the problem. > > What have you used to replace console.log(reallyUsefulStuff) when you have > had to disable FireBug? Opera and opera.postError() ;-) By the time I needed Firebug again, the problem had somehow resolved itself, probably as a result of a Firebug update. -- stefan |