Re: D6 Error opening image

Hi Bill,

Thanks for the suggestions!

A couple of days ago I was deploying a different project. One of the
packages had a #publishedAspectsOfInstances method in it. If I
installed the packages in a fresh image, then immediately deployed
(then dismissed the MessageBox warning me about the development system
dependence), the resulting togo would immediately crash when run.

If I saved the image, removed the offending method, and then deployed
... no crash. I was able to repeat this a couple of times.

I did find a recent thread: "Primitive Process>>primTerminate failed
(0)" that described something very similar to what I was/am seeing.
Like what was described in that thread, if I wait around, eventually
the app will show itself.

DebugView shows:

[3332] WARNING: Ignored interrupt 18 to terminated process a
Process('Main' base 09480000 frame=nil)
[3332] Dolphin: Writing dump to ...
[3332] WARNING: No processes are Ready to run

I know it sounds unbelievable, but I have since found that the only
difference between getting the "Primitive Process>>primTerminate failed
(0)" error and not getting it is:
- Case 1/ Install the packages and then deploy the executable
immediately, results in the "primTerminate failed " error.
- Case 2/ Install the packages, then save/exit/restart the image and
then deploy ... no error.

I compared the deployment manifests with an xml comparison tool and the
only significant differences I could find were:

- Togo was 100kb larger in Case 1/ than Case 2/
- ComDlgLibrary had 0 instances in Case 1/ , but had 1 instance in
Case 2/
- ShellLibrary had 1 instance in Case 1/ , but had 0 instances in
Case 2/
- Case 1/ had an extra 11 ExternalHandle instances which is explained
by 11 extra Icon instances
- The ImageStripperProgress class was stripped in Case 1/ but not
Case 2/

There were a few other changes in the number of strings/symbols etc,
but they looked like they were as a result of the extra class being
stripped. What was reported in the respective manifests did not, in my
mind, add up to a 100kb difference between the two togos.

FWIW: I have not been able to reproduce this with a simple package, In
any case, I have a work around and I typically
install/save/exit/restart when deploying anyway because it usually cuts
5 to 10kb off the size of the togo ... however I have never seen a drop
of 100kb before.

Steve
--
Steve Waring

.

Relevant Pages