Re: D6 Error opening image
- From: Bill Schwab <bschwab@xxxxxxxxxxxxx>
- Date: Fri, 24 Mar 2006 20:18:32 -0500
Steve,
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.
Going way back, I had to hack the idle loop for benefit of COM apps that would stall in absence of user input. When I hear of delays followed by an app starting, I get flashbacks.
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
Is that "the" main process, or another that was is having trouble going away?
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 wouldn't predict it, but it's not really shocking, especially if the loading and deploying is scripted vs. user driven. Have you tried adding a few explicit #collectGarbage and #administerLastRites sends?
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/
Interesting. There are things that are cleared on startup, though I would expect most of this stuff to be recreated when the IDE reloads.
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.
I frequently see changes of 100k or so in normal use. It could simply be the fortunes of dynamic memory management - or does Dolphin trim the excess when it saves such that that makes no sense???
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.
I like to get an image running nicely, test passing, etc., and then deploy from it. I know many people like to deploy from a clean image, but even if I were to do that, I would still get everying loaded and save before deploying. To do otherwise could be quite slow. Just restarting/stripping from a batch file takes 30 minutes for everything that I deploy.
Have a good one,
Bill
--
Wilhelm K. Schwab, Ph.D.
bills@xxxxxxxxxxxxxxxxxxxx
.
- Follow-Ups:
- Re: D6 Error opening image
- From: swaring
- Re: D6 Error opening image
- References:
- D6 Error opening image
- From: swaring
- Re: D6 Error opening image
- From: Bill Schwab
- Re: D6 Error opening image
- From: swaring
- Re: D6 Error opening image
- From: Bill Schwab
- Re: D6 Error opening image
- From: swaring
- D6 Error opening image
- Prev by Date: Re: How to write a simple Code Rewrite for x -> self x?
- Next by Date: Re: ( picoVerse-:( convert Generators from version 2.1 to version 6 ) )
- Previous by thread: Re: D6 Error opening image
- Next by thread: Re: D6 Error opening image
- Index(es):
Relevant Pages
|