[softwarelist] Re: OvationPro and memory allocation
- From: Tank <webmaster@xxxxxxxxxxxxxxx>
- To: davidpilling@xxxxxxxxxxxxx
- Date: Thu, 13 Jul 2006 16:27:42 +0100
In message <4e45c34869lists-nospam@xxxxxxxxx> you wrote:
> In article <4e45c294d2chris@xxxxxxxxxxxxxxxxxxxxx>,
> Chris Johnson <chris@xxxxxxxxxxxxxxxxxxxxx> wrote:
> > Could you amplify this a little. I have tried, and I see no flicker in
> > either the Ovation Pro application task slot, or in the Ovation Pro
> > dynamic area memory. This is both with a single document loaded, and
> > several documents loaded. The application slot does sometimes increase by
> > a 4K unit when a page reformat is caused by typing into the middle of the
> > document, which has embedded pictures, but no flickering.
>
> Using OvationPro v2.77 on a 512MB Iyonix with ROS 5.11, open a new OvPro
> document.
>
> Open 'Tasks' window.
>
> Just type random gobbledegook into OvPro default page. The 'OvationPro'
> application space constantly flickers by claiming and releasing an extra 4K.
>
> Does it all the time here, so should be easily reproducible.
>
No change here with v2.77 128MB RO 5.11
Tank
--
webmaster@xxxxxxxxxxxxxxx
Iyonix PC
- References:
- [softwarelist] OvationPro and memory allocation
- From: Paul Vigay
- [softwarelist] Re: OvationPro and memory allocation
- From: Chris Johnson
- [softwarelist] Re: OvationPro and memory allocation
- From: Paul Vigay
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] OvationPro and memory allocation
- From: Paul Vigay
- [softwarelist] Re: OvationPro and memory allocation
- From: Chris Johnson
- [softwarelist] Re: OvationPro and memory allocation
- From: Paul Vigay