[iyonix-support] Re: Lazy Task Swapping on Iyonix/RISC OS 5.11

On Fri 23 Jun, Ste (PlusNet) wrote:
> 
> On 23 Jun, jb <jwb@xxxxxxxxxx> wrote:
> > Hi Roger
> > having examined the sprite data you sent:
> >
> > the 'wrong data' is 8k in length starting at offset &298ffc, and is, or
> > appears to be, font data.
> 
> More specifically, it includes a font list similar to that output by the
> *FontCat command. I can't see any point in Organizer's workspace where it
> stores this kind of structure so I'd be tempted to rule that application out
> for the time being.
> 
> Also, I use POPstar and Organizer all day, every day, (this Iyonix is on
> 24/7 and has been for years). I have never seen the effect which is being
> described in this thread. I'm running RO 5.09 in 1280x1024x16M if that
> helps. I have sprite backdrops and 128MB RAM.
> 
> > the fact that it starts at 298ffc is intriguing, because if was saved by
> > *screensave, then I suspect it would have omitted the first 4 bytes of the
> > screen area, hence effective start point is on a 4k page boundary. i.e. it
> > is 2 pages of data. who owned it I'm not sure (options include your 2
> > progs, and also the fontmanager ..)
> 
> Might be looking at the contents of any suspect applications' wimpslots (you
> can capture them with Zap) and then searching for something along the lines
> of "Homerton.Medium.Oblique" so see if you can spot any lists similar to the
> *FontCat output.
> 
> I'd also check any dynamic areas associated with the applications - maybe
> also the "PCI shared memory" area to see if something there from there is
> being 'leaked' into other appslots (or the screen memory).

Am I correct in believing that only wimp slot memory is remapped in LTS?
And that wimp slot memory is only used by the application and its
variables/data?

The suggestion has been made that the backdrop may not be the only memory to
be being corrupted by the bug and that corruption of other memory could be
causing some hangs, the most obvious other memory would be wimpslot but..

If application memory was being corrupted then I'd expect BASIC programes to
fall over with various errors e.g. no such variable at line X or No TO at
line Y but no reports of these sort of errors seem to have been made.

To my simple mind this would suggest that whatever the problem is that is
causing backdrop corruption is not corrupting wimp slot memory, corruption
of other memory is of course possible but seems strange with LTS appearing
to be the cause.
I wonder if the problem could be something not directly related to LTS but
something occuring whilst LTS is in progress, say under interrupt, LTS not
returning cleanly or...

n.b. Variations is written in BASIC I believe!


Chris Evans

-- 
CJE Micro's / 4D                'RISC OS Specialists'
Telephone: 01903 523222             Fax: 01903 523679
chris@xxxxxxxxxxxxxxx     http://www.cjemicros.co.uk/
78 Brighton Road, Worthing, West Sussex,     BN11 2EN
The most beautiful thing anyone can wear, is a smile!


---
To alter your preferences or leave the group, 
visit http://www.freelists.org/list/iyonix-support
Other info via http://www.freelists.org/webpage/iyonix-support

Other related posts: