[softwarelist] OvationPro and memory allocation
- From: Paul Vigay <lists-nospam@xxxxxxxxx>
- To: davidpilling@xxxxxxxxxxxxx
- Date: Thu, 13 Jul 2006 10:18:07 +0100
I've been doing some investigations into suspected memory problems on an
Iyonix, suspecting a potential bug in the Lazy Task Swapping code
(previously discussed on the Iyonix mailing list), and one common
denominator is that OvationPro is always loaded when I encounter problems.
Looking at the task display, I notice that the application task space for
OvationPro constantly flichers when entering text into an OvPro window.
This would imply that OvPro is claiming and releasing wimp application
memory blocks on a more or less constant basis.
Is it supposed to do this, as I have a suspicion it's possibly contributing
to a failure of LTS under certain conditions on the Iyonix.
I guess this is a question mainly aimed at David :-) as it's of a somewhat
technical nature, but if you want more information, please email me and I
can provide a test which (9 times out of 10) causes the problem to occur.
Paul
--
Paul Vigay __\\|//__ Life,
(` o-o ') the Universe
http://www.vigay.com -----ooO-(_)-Ooo------ & Everything ------
They who commit a mistake and do not correct it commit another mistake.
- Follow-Ups:
- [softwarelist] Re: OvationPro and memory allocation
- From: Chris Johnson
- [softwarelist] Re: OvationPro and memory allocation
- From: David Pilling
Other related posts:
- » [softwarelist] OvationPro and memory allocation
- » [softwarelist] Re: OvationPro and memory allocation
- » [softwarelist] Re: OvationPro and memory allocation
- » [softwarelist] Re: OvationPro and memory allocation
- » [softwarelist] Re: OvationPro and memory allocation
- » [softwarelist] Re: OvationPro and memory allocation
- » [softwarelist] Re: OvationPro and memory allocation
- » [softwarelist] Re: OvationPro and memory allocation
- » [softwarelist] Re: OvationPro and memory allocation
- » [softwarelist] Re: OvationPro and memory allocation
- » [softwarelist] Re: OvationPro and memory allocation
- » [softwarelist] Re: OvationPro and memory allocation
- » [softwarelist] Re: OvationPro and memory allocation
- » [softwarelist] Re: OvationPro and memory allocation
- » [softwarelist] Re: OvationPro and memory allocation
- » [softwarelist] Re: OvationPro and memory allocation
- » [softwarelist] Re: OvationPro and memory allocation
- » [softwarelist] Re: OvationPro and memory allocation
- » [softwarelist] Re: OvationPro and memory allocation
- » [softwarelist] Re: OvationPro and memory allocation
- » [softwarelist] Re: OvationPro and memory allocation
- » [softwarelist] Re: OvationPro and memory allocation
- » [softwarelist] Re: OvationPro and memory allocation
- » [softwarelist] Re: OvationPro and memory allocation
- » [softwarelist] Re: OvationPro and memory allocation
- » [softwarelist] Re: OvationPro and memory allocation
- » [softwarelist] Re: OvationPro and memory allocation
- » [softwarelist] Re: OvationPro and memory allocation
- » [softwarelist] Re: OvationPro and memory allocation
- » [softwarelist] Re: OvationPro and memory allocation
- » [softwarelist] Re: OvationPro and memory allocation
- » [softwarelist] Re: OvationPro and memory allocation
- » [softwarelist] Re: OvationPro and memory allocation
- » [softwarelist] Re: OvationPro and memory allocation
- » [softwarelist] Re: OvationPro and memory allocation
- » [softwarelist] Re: OvationPro and memory allocation
- [softwarelist] Re: OvationPro and memory allocation
- From: Chris Johnson
- [softwarelist] Re: OvationPro and memory allocation
- From: David Pilling