#61 reproduceable runtime error on WinXP

2.05 beta
closed
nobody
None
5
2008-08-26
2007-01-23
ward
No

1) Open Apohysis 2.05 beta.
2) Choose any random generated flame (it does not mather which)
3) Go to menu 'Script -> Open' and select the premade 'Animation render' script.
For eliminating communication problems, this is the script:

{ ************************************ }
{ }
{ Animation rendering example script. }
{ Mark Townsend, September 2003. }
{ }
{ *************************************}

{ Set the size of the rendered frames. }
Renderer.Width := 320;
Renderer.Height := 240;
{ Need to calculate the scale of the
flame for the image size... }
SetRenderBounds;
{ I set sample density set for reasonable
speed. Increase it for higher quality images,
which will take longer to render. The other
Flame parameters will use the default display
values. }
Flame.SampleDensity := 10;
for j := 0 to 99 do // 100 frames,
begin
for i := 0 to Transforms - 1 do
begin
SetActiveTransform(i);
{ 360 degrees / 100 will give an
animation that cycles seamlessly. }
Rotate(3.6);
end;
{ The filename needs to be changed for each
frame, otherwise they'd just be rendered
over and over to the same file. I use 00.jpg
to 99.jpg }
Renderer.Filename := 'c:\renders\' + Format('%.2d', [j]) + '.bmp';
Render;
end;
UpdateFlame := False;

4) Run this script.
5) At the end of rendering 00.bmp the application hangs
6) When trying to press the 'cancel' button you get the following error message:
"Runtime error
Undefined instruction"
Press ok on this message.
7) Press cancel again in the 'Rendering filename' window, now you see the following error message:
"Access violation at address 0042ECD8 in module Apophysis205beta2.exe. Write of address 02ABC2FD"

8) You have to close the application.

I'm using Apophysis on WindowsXP.
I've also tested this version on a Windows2000, but there the problem does not occur.

Discussion

  • ward
    ward
    2007-01-23

    Logged In: YES
    user_id=1699272
    Originator: YES

    He, I've managed to perform the script when turning multithreaded setting OFF.
    This should help you localize the problem.
    With this workaround, the bug can be set to a lower priority.

    The application on my Win2000 computer was configured with multithreading OFF, so that's why it didn't crash the first place.

    Summary: the application has a problem in executing a rendering operation via script with multithreading set to value 8.

    kind regards,

    Ward

     
  • Peter Sdobnov
    Peter Sdobnov
    2008-08-26

    • status: open --> closed