[softwarelist] Re: OvnPro 2.77 type 5 errors

In article <lFyjIqAgV1XJFwT9@xxxxxxxxxxxxxxxxxxx>,
   David Pilling <flist@xxxxxxxxxxxxxxxxxxx> wrote:
> In message <5017ab9e1dasgard@xxxxxxxxxxxxxx>, Keith Hopper 
> <asgard@xxxxxxxxxxxxxx> writes
> >herring (I think!).  OK! Save as DDF - reloading the DDF reveals the same
> >problems!

> DDL...

     Ouch! I consider myself duly castigated!

> Problems like this can be due to external problems, for example there 
> may be a bug in part of RISC OS, however the most likely causes are bugs 
> in Ovation Pro.

     I have a suspicion it is to do with the IFC from OvnPro - more on that
later.

> You seem to be pointing to graphics. One idea is to use the View menu to 
> turn off rendering of pictures and see if the document still crashes.

     Turned off - no crash. I have been recently getting OvnPro to crash
just by sliding up and down the scroll bar several times - with images off
this can be done in any way at any speed and the programme does not crash.
Turn graphics back on -  and a couple of sweeps with the scroll bar and the
erorr has occurred.

> It would also be interesting to know if the document crashes when 
> printed, since printing consists of rendering the whole document.

     I have printed just the offending page - and the whole document - in
glorious technicolor - with no crash! After printing, a couple of 'sweeps'
with the scroll bar and the crash recurs.

     I note, however, that after three crashes there are three OvnPro
dynamic areas - at one stage I had fifteen of them which led to Pluto
reporting "Unable to allocate logical address space" when I clicked on a
URL in an attempt to download the latest AWViewer as suggested by Brian
Howlett.

     As you may imagine, I did not stop trying to elminate causes having
sent my earlier message. I took an empty document and started adding frame
by frame until I obtained the crash. This test document is about half a
megabyte compressed.

     I have found the following things provoke the crash - moving up and
down one document with the offending grouped frame (by the way ungrouping
the frames makes no difference) - and trying to copy that frame to another
document - the crash occurs when the image is about to be rendered on the
second document.

     This has led me to wonder whether the problem is related to redrawing
when some cache limit has been reached, a region is put out of the cache
and thus re-rendering is necessary.

     The reason that this comes to mind is that I have a document
containing just the one grouped frame which, when added to the test
document, causes the crash. I can fill this other document with as many
copies of the offending frame (group) as I like and the crash does not
occur whatever I do. Put it into the test document and the crash occurs
after a few 'sweeps' of the scroll bar.

     The magazine is actually the first document that I can remember
producing with more than one Artworks image (there will eventually be some
20 - plus a further dozen or so jpeg images). The total document size will
only be about 5Mb when complete - so I am sure document size has nothing to
do with it. I have documents of hundreds of pages (with no Artworks images)
with which I have had no problem. There might, however, nevertheless be a
memory problem.

     After printing, there is a 56Mb dynamic area still allocated to
AWRender Crystal supp - which I thought that OvnPro would have released.
Perhaps that is awaiting normal OvnPro termination (which, of course,
hasn't occurred because it crashed)?  In addition to this I have three
OvnPro dynamic areas - one of 1104kb, the other two of 1108kb. All,
correspond to crashes of the same document - so why the different sizes? Is
this, I ask myself, a further clue?

     I hope what I have done may offer a useful hint as to where to look
next!

               Thanks,

                         Keith

-- 
Inspired!
To unsubscribe or subscribe goto: http://www.freelists.org/list/davidpilling

Other related posts: