OK, but this was mentioned in the article. I think the file name was
corrupted by wordpress.
Sebastian
westor schrieb:
> Sebastian, I dropped a comment there:
> The file name has to be case sensitive: XmlHttpTransport.js instead of
> xmlhttptransport.js
> Torsten
>
>
> Sebastian Werner wrote:
Sebastian, I dropped a comment there:
The file name has to be case sensitive: XmlHttpTransport.js instead of
xmlhttptransport.js
Torsten
Sebastian Werner wrote:
>
> Hi all!
>
> I have posted a news article related to this topic. Please have a look
> here:
> http://news.qooxdoo.org/memory-issue
Oops. Sorry for the typo. I've added Andreas and corrected your name.
Thanks for the feedback.
Sebastian
Hugh Gibson schrieb:
>> I have posted a news article related to this topic. Please have a
>> look here:
>> http://news.qooxdoo.org/memory-issue-in-xmlhttp-fixed
>
> Ah, thanks, but I'm not
> I have posted a news article related to this topic. Please have a
> look here:
> http://news.qooxdoo.org/memory-issue-in-xmlhttp-fixed
Ah, thanks, but I'm not that big... Huge?
Also, Andreas Junghans came up with the initial clue about the root of
the problem.
Hugh
--
Hi all!
I have posted a news article related to this topic. Please have a look here:
http://news.qooxdoo.org/memory-issue-in-xmlhttp-fixed
Sebastian
Fabian Jakobs schrieb:
> Hello Hugh,
>>> I am not sure if this directly bring out a new release. But I would
>>> be very happy to fix this in the
Hello Hugh,
>> I am not sure if this directly bring out a new release. But I would
>> be very happy to fix this in the current branch.
>>
>> Thank you for your investigation. If you can prepare a patch or
>> send the the modified files I will do my best to integrate them as
>> soon as possible i
Hi Hugh,
Fabian will have a look at your patch immediately. We will consider
to break our policy and update the demos to a non-release version.
However I don't see the benefit of this for the moment. We will test
your change, which looks quite straightforward, and will officially
bring out
> I am not sure if this directly bring out a new release. But I would
> be very happy to fix this in the current branch.
>
> Thank you for your investigation. If you can prepare a patch or
> send the the modified files I will do my best to integrate them as
> soon as possible into the SVN.
>
>
Hi Hugh,
I am not sure if this directly bring out a new release. But I would be
very happy to fix this in the current branch.
Thank you for your investigation. If you can prepare a patch or send the
the modified files I will do my best to integrate them as soon as
possible into the SVN.
Thank
Sebastian/Andreas E, I would strongly suggest that this is a very good
reason to bring forward 0.7.3.
I think you should look at your testing procedures as something as
fundamental as this shouldn't be allowed to slip through the net for so
long.
> The problem is in this code in the destructor in
Hi Hugh,
Am 24.09.2007 um 17:21 schrieb Hugh Gibson:
> It appears that any remote request using XMLHttpRequest leaks
> memory in
> IE7. In a testcase running here, a regular operation (polling the
> server)
> which has around 5 POST requests sent off in quick succession consumes
> 170 KB. Tha
As hinted at elsewhere, I've been trying to track down a memory leak
issue in IE7 and 0.7.x.
It appears that any remote request using XMLHttpRequest leaks memory in
IE7. In a testcase running here, a regular operation (polling the server)
which has around 5 POST requests sent off in quick success
12 matches
Mail list logo
