| Groups | Blog | Home |
asp.net webservices : Memory leak in IE javascript with webservice.htc
I'm working on an application where I need to be able to call a .net
web service from javascript. I found the webservice.htc file, and was able to create a page that worked just fine, except that the memory usage of iexplore.exe began to increase without limit as the service was called. To demonstrate this, I tried the following script, which showed the increase very quickly by continuously calling the service. Since useService is the only method being called, this is likely where the problem lies. Is there a fix for this problem yet? Thanks, Chris <html> <head> <script language="JavaScript"> function init() { service.useService("http://testServer/testcti/service1.asmx?WSDL","Test"); call(); } function call() { service.TestCTI.callService("AgentEventWait",1000,100,"ice1"); } function onWSresult() { call(); } </script> </head> <body onload="init()"> <div id="service" style="behavior:url(webservice.htc)" onresult="onWSresult()"> </div> </body>
IE has lots of memory leaks, not surprising that that there is a leak
calling xmlhttp. I doubt that any fix will be coming, as the soap behavior calls for increased security settings with xp-sp2. switch to the standard hidden frame approach for IE, and save soap calls for mozilla/netscape which have it in. -- bruce (sqlwork.com) [quoted text, click to view] "Chris Bardon" <cmbardon@engmail.uwaterloo.ca> wrote in message news:5c2b81.0409271111.60bc555d@posting.google.com... > I'm working on an application where I need to be able to call a .net > web service from javascript. I found the webservice.htc file, and was > able to create a page that worked just fine, except that the memory > usage of iexplore.exe began to increase without limit as the service > was called. To demonstrate this, I tried the following script, which > showed the increase very quickly by continuously calling the service. > Since useService is the only method being called, this is likely where > the problem lies. Is there a fix for this problem yet? > > Thanks, > > Chris > > > <html> > <head> > <script language="JavaScript"> > > function init() > { > service.useService("http://testServer/testcti/service1.asmx?WSDL","Test"); > call(); > } > > function call() > { > service.TestCTI.callService("AgentEventWait",1000,100,"ice1"); > } > > function onWSresult() > { > call(); > } > </script> > </head> > <body onload="init()"> > <div id="service" style="behavior:url(webservice.htc)" > onresult="onWSresult()"> > </div> > </body> > </html>
Chris,
You've setup call() to call itself until run IE runs out of memory. 'onresult' is for checking the result of a callService(). In your 'onWSresult()' Javascript function don't call call(), check for the following function onWSresult() { if((event.result.error)&&(iCallID==event.result.id)) { var xfaultcode = event.result.errorDetail.code; var xfaultstring = event.result.errorDetail.string; var xfaultsoap = event.result.errorDetail.raw; // Add code to output error information here alert("Error "); } } The way you have it now function onWSresult() { call(); } onWSresult() calls call() over and over again because you've setup a onresult to fire an event after AgentEventWait is finished. Once the first call() is finished, which is your call to your AgentEventWait, that's when your onresult event gets fired, which is your onWSresult() function. onWSresult() calls call() again, once that call is finished, again your AgentEventWait, then that's when your onresult event gets fired again, which is your onWSresult(). To verify that this is the case, use DbgCLR.exe and set a breakpoint inside of AgentEventWait, then call your HTML page that calls the webservice. You'll see AgentEventWait being called again and again. Gabe [quoted text, click to view] "Chris Bardon" <cmbardon@engmail.uwaterloo.ca> wrote in message news:5c2b81.0409271111.60bc555d@posting.google.com... > I'm working on an application where I need to be able to call a .net > web service from javascript. I found the webservice.htc file, and was > able to create a page that worked just fine, except that the memory > usage of iexplore.exe began to increase without limit as the service > was called. To demonstrate this, I tried the following script, which > showed the increase very quickly by continuously calling the service. > Since useService is the only method being called, this is likely where > the problem lies. Is there a fix for this problem yet? > > Thanks, > > Chris > > > <html> > <head> > <script language="JavaScript"> > > function init() > { > service.useService("http://testServer/testcti/service1.asmx?WSDL","Test"); > call(); > } > > function call() > { > service.TestCTI.callService("AgentEventWait",1000,100,"ice1"); > } > > function onWSresult() > { > call(); > } > </script> > </head> > <body onload="init()"> > <div id="service" style="behavior:url(webservice.htc)" > onresult="onWSresult()"> > </div> > </body> > </html>
Opps, meant to say until the OS runs out of memory.
[quoted text, click to view] "Gabe Garza" <spam@nospam.com> wrote in message news:4k%5d.20491$QJ3.7333@newssvr21.news.prodigy.com... > Chris, > > You've setup call() to call itself until run IE runs out of memory. > 'onresult' is for checking the result of a callService(). > In your 'onWSresult()' Javascript function don't call call(), check for the > following > > function onWSresult() > { > if((event.result.error)&&(iCallID==event.result.id)) > { > var xfaultcode = event.result.errorDetail.code; > var xfaultstring = event.result.errorDetail.string; > var xfaultsoap = event.result.errorDetail.raw; > > // Add code to output error information here > alert("Error "); > } > } > > The way you have it now > > function onWSresult() > { > call(); > } > > onWSresult() calls call() over and over again because you've setup a > onresult to fire an event after AgentEventWait is finished. > > Once the first call() is finished, which is your call to your > AgentEventWait, that's when your onresult event gets fired, which is your > onWSresult() function. > onWSresult() calls call() again, once that call is finished, again your > AgentEventWait, then that's when your onresult event gets fired again, which > is your onWSresult(). > > To verify that this is the case, use DbgCLR.exe and set a breakpoint inside > of AgentEventWait, then call your HTML page that calls the webservice. > You'll see AgentEventWait being called again and again. > > Gabe > > > "Chris Bardon" <cmbardon@engmail.uwaterloo.ca> wrote in message > news:5c2b81.0409271111.60bc555d@posting.google.com... > > I'm working on an application where I need to be able to call a .net > > web service from javascript. I found the webservice.htc file, and was > > able to create a page that worked just fine, except that the memory > > usage of iexplore.exe began to increase without limit as the service > > was called. To demonstrate this, I tried the following script, which > > showed the increase very quickly by continuously calling the service. > > Since useService is the only method being called, this is likely where > > the problem lies. Is there a fix for this problem yet? > > > > Thanks, > > > > Chris > > > > > > <html> > > <head> > > <script language="JavaScript"> > > > > function init() > > { > > service.useService("http://testServer/testcti/service1.asmx?WSDL","Test"); > > call(); > > } > > > > function call() > > { > > service.TestCTI.callService("AgentEventWait",1000,100,"ice1"); > > } > > > > function onWSresult() > > { > > call(); > > } > > </script> > > </head> > > <body onload="init()"> > > <div id="service" style="behavior:url(webservice.htc)" > > onresult="onWSresult()"> > > </div> > > </body> > > </html> > >
Thanks Bruce-is there somewhere that details this "hidden frame"
approach that you're talking about? I tried a version where I had a frame invoking the web service using an HTTP GET call and the page's location property, but there was no way that I could get the returned XML to the main frame without an access violaton. Since the web service call that I'm making can block, I can't really use the auto refresh property to perpetually call it. Ideally, I'd like to be able to do what I had in my script, which is to call the service, handle the return, then call it again. Any idea how I can accomplish this? [quoted text, click to view] "bruce barker" <nospam_brubar@safeco.com> wrote in message news:<uu4s6xMpEHA.132@TK2MSFTNGP14.phx.gbl>...
> IE has lots of memory leaks, not surprising that that there is a leak > calling xmlhttp. I doubt that any fix will be coming, as the soap behavior > calls for increased security settings with xp-sp2. switch to the standard > hidden frame approach for IE, and save soap calls for mozilla/netscape which > have it in. >
Don't see what you're looking for? Try a search.
|
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
December 2007
January 2008
February 2008
March 2008
April 2008
May 2008
June 2008
| home · blog · groups | Questions? Comments? Contact the dn |