|
|
Posted by Aaron Saray on 09/12/07 02:15
On Sep 11, 10:03 am, melma...@gmail.com wrote:
> On 10 Wrz, 21:19, Sanders Kaufman <bu...@kaufman.net> wrote:
>
>
>
> > melma...@gmail.com wrote:
> > > I have used sessions and forced garbage collector
> > > to clean the memory with the probability 100%
> > > (reconfiguring php.ini file)
> > > and I called this script X times. The memory was not freed at all!
>
> > > But I have discovered that it is Windows bug (see my reply to Aaron)
>
> > In the Zend Platform docs, they point out that while Windows servers are
> > adequate for most development, they should not be used for production.
>
> > This shell problem is exactly why.
>
> > This same bug is why Windows became such a target for viruses - the real
> > ones, not the scripties.
>
> > Those Seattle Republicans play fast-and-loose with memory management.
>
> After long hours of fighting and testing I have fixed the problem.
> It was caused by an additional firewall installed on both computers
> used by me for testing process. When I uninstalled it memory leak
> disappeared.
>
> Thanks all for help.
> Best regards
> Melmack
What firewalls were they? I haven't thought about that - heh - its
been such a long time since I thought about those (about 2 years when
I used to work at an ISP). I guess that makes sense... with either a
virus protection program or a firewall - they're going to scan spawned
processes... but woudln't it be the a/v or firewall process that gets
the memory spike? Any other details would be cool - I'm rather
curious now.
Navigation:
[Reply to this message]
|