[7.5][RTP] Disabling emergency evaluator and process monitor?

What would be the appropriate action? Right now I would much rather treat it as terminal exception and terminate the image than have a process monitor coming up on end-users machine. Are you suggesting there's a clean way of hooking up a handler to low space event?

Cheers!

-Boris
(Sent from a BlackBerry)

----- Original Message -----
From: Terry Raymond <[hidden email]>
To: Boris Popov; [hidden email] <[hidden email]>
Sent: Tue May 29 17:49:57 2007
Subject: RE: [7.5][RTP] Disabling emergency evaluator and process monitor?

Boris

It seems to me that you want the low space action to do
something else appropriate.

Terry

===========================================================
Terry Raymond
Crafted Smalltalk
80 Lazywood Ln.
Tiverton, RI  02878
(401) 624-4517      [hidden email]
<http://www.craftedsmalltalk.com>
===========================================================

> -----Original Message-----
> From: Boris Popov [[hidden email]]
> Sent: Tuesday, May 29, 2007 6:38 PM
> To: Terry Raymond; [hidden email]
> Subject: RE: [7.5][RTP] Disabling emergency evaluator and process monitor?
>
> Oh, Ctrl+\ can also be fixed the same way with,
>
> allProcessInterruptKey
>   RuntimeSystem isRuntime ifTrue: [^nil].
>   AllProcessInterruptKey ifNil: [self initializeProcessInterrupt].
>   ^AllProcessInterruptKey < 0
>       ifTrue: [AllProcessInterruptKey negated]
>       ifFalse: [AllProcessInterruptKey < 16r20000
>                    ifTrue: [Character value: AllProcessInterruptKey]
>                    ifFalse: [AllProcessInterruptKey]]
>
> Now on to making sure that #interruptProcessForLowSpace doesn't come up
> with a process monitor and I think that'll be the last of it, any other
> places I might be missing?
>
> Cheers!
>
> -Boris
>
> --
> +1.604.689.0322
> DeepCove Labs Ltd.
> 4th floor 595 Howe Street
> Vancouver, Canada V6C 2T5
> http://tinyurl.com/r7uw4
>
> [hidden email]
>
> CONFIDENTIALITY NOTICE
>
> This email is intended only for the persons named in the message
> header. Unless otherwise indicated, it contains information that is
> private and confidential. If you have received it in error, please
> notify the sender and delete the entire message including any
> attachments.
>
> Thank you.
>
> > -----Original Message-----
> > From: Boris Popov [[hidden email]]
> > Sent: Tuesday, May 29, 2007 3:18 PM
> > To: Terry Raymond; [hidden email]
> > Subject: RE: [7.5][RTP] Disabling emergency evaluator and process
> monitor?
> >
> > Thanks, I found both easily and was secretly hoping for an AR instead
> ;)
> >
> > Looks like the emergency evaluator can be suppressed with,
> >
> > InputState class>>interruptKeyValue
> >
> > RuntimeSystem isRuntime ifTrue: [^nil].
> > ^InterruptKey < 0
> >     ifTrue: [InterruptKey negated]
> >     ifFalse: [InterruptKey < 16r20000
> >                ifTrue: [Character value: InterruptKey]
> >                ifFalse: [InterruptKey]].
> >
> > but ProcessMonitorClient seems to be wired in much tighter and
> whatever
> > overrides I come up I don't want to have to maintain for long. Just
> > suggesting that both should not be available in the runtime, that's
> all.
> >
> > -Boris
> >
> > --
> > +1.604.689.0322
> > DeepCove Labs Ltd.
> > 4th floor 595 Howe Street
> > Vancouver, Canada V6C 2T5
> > http://tinyurl.com/r7uw4
> >
> > [hidden email]
> >
> > CONFIDENTIALITY NOTICE
> >
> > This email is intended only for the persons named in the message
> > header. Unless otherwise indicated, it contains information that is
> > private and confidential. If you have received it in error, please
> > notify the sender and delete the entire message including any
> > attachments.
> >
> > Thank you.
> >
> > > -----Original Message-----
> > > From: Terry Raymond [[hidden email]]
> > > Sent: Tuesday, May 29, 2007 3:08 PM
> > > To: Boris Popov; [hidden email]
> > > Subject: RE: [7.5][RTP] Disabling emergency evaluator and process
> > monitor?
> > >
> > > Boris
> > >
> > > The code that activates them is in
> > > EventSensor>>keyAt:character:alternative:down:.
> > >
> > > Terry
> > >
> > > ===========================================================
> > > Terry Raymond
> > > Crafted Smalltalk
> > > 80 Lazywood Ln.
> > > Tiverton, RI  02878
> > > (401) 624-4517      [hidden email]
> > > <http://www.craftedsmalltalk.com>
> > > ===========================================================
> > >
> > > > -----Original Message-----
> > > > From: Boris Popov [[hidden email]]
> > > > Sent: Tuesday, May 29, 2007 5:24 PM
> > > > To: [hidden email]
> > > > Subject: [7.5][RTP] Disabling emergency evaluator and process
> > monitor?
> > > >
> > > > In our RTP'ed runtimes hitting Ctrl-Y or walking into an
> > out-of-memory
> > > > condition results in these two tools that have no place in built
> > > > applications IMHO. I'd noticed the 'Install emergency evaluator as
> > > > dialog' setting in RTP, but it didn't seem to have any noticeable
> > effect
> > > > and I didn't see anything relating to process monitor at all.
> Should
> > > > these two be disabled in a runtime by default? Anyone have a patch
> > to
> > > > disable them before I go on a safari myself?
> > > >
> > > > -Boris
> > > >
> > > > --
> > > > +1.604.689.0322
> > > > DeepCove Labs Ltd.
> > > > 4th floor 595 Howe Street
> > > > Vancouver, Canada V6C 2T5
> > > > http://tinyurl.com/r7uw4
> > > >
> > > > [hidden email]
> > > >
> > > > CONFIDENTIALITY NOTICE
> > > >
> > > > This email is intended only for the persons named in the message
> > > > header. Unless otherwise indicated, it contains information that
> is
> > > > private and confidential. If you have received it in error, please
> > > > notify the sender and delete the entire message including any
> > > > attachments.
> > > >
> > > > Thank you.

I agree. Hence I suggest that 7.6 should,

1. Change default to anything but an obscure and potentially dangerous tool popping up

2. Add a configuration option to change that behavior with a custom handler

Oh, and disable emergency evaluator completely at runtime.

Cheers!

-Boris
(Sent from a BlackBerry)

----- Original Message -----
From: Terry Raymond <[hidden email]>
To: Boris Popov; [hidden email] <[hidden email]>
Sent: Tue May 29 19:05:30 2007
Subject: RE: [7.5][RTP] Disabling emergency evaluator and process monitor?

Boris



It would seem to me that the action should invoke a block like

the emergency exception handler. I would think that what actually

occurs would depend on your specific application.



Terry

===========================================================
Terry Raymond
Crafted Smalltalk
80 Lazywood Ln.
Tiverton, RI  02878
(401) 624-4517      [hidden email]
<http://www.craftedsmalltalk.com>
===========================================================

________________________________

From: Boris Popov [[hidden email]]
Sent: Tuesday, May 29, 2007 9:09 PM
To: [hidden email]; [hidden email]
Subject: Re: [7.5][RTP] Disabling emergency evaluator and process monitor?



What would be the appropriate action? Right now I would much rather treat it as terminal exception and terminate the image than have a process monitor coming up on end-users machine. Are you suggesting there's a clean way of hooking up a handler to low space event?

Cheers!

-Boris
(Sent from a BlackBerry)

----- Original Message -----
From: Terry Raymond <[hidden email]>
To: Boris Popov; [hidden email] <[hidden email]>
Sent: Tue May 29 17:49:57 2007
Subject: RE: [7.5][RTP] Disabling emergency evaluator and process monitor?

Boris

It seems to me that you want the low space action to do
something else appropriate.

Terry

===========================================================
Terry Raymond
Crafted Smalltalk
80 Lazywood Ln.
Tiverton, RI  02878
(401) 624-4517      [hidden email]
<http://www.craftedsmalltalk.com>
===========================================================

> -----Original Message-----
> From: Boris Popov [[hidden email]]
> Sent: Tuesday, May 29, 2007 6:38 PM
> To: Terry Raymond; [hidden email]
> Subject: RE: [7.5][RTP] Disabling emergency evaluator and process monitor?
>
> Oh, Ctrl+\ can also be fixed the same way with,
>
> allProcessInterruptKey
>   RuntimeSystem isRuntime ifTrue: [^nil].
>   AllProcessInterruptKey ifNil: [self initializeProcessInterrupt].
>   ^AllProcessInterruptKey < 0
>       ifTrue: [AllProcessInterruptKey negated]
>       ifFalse: [AllProcessInterruptKey < 16r20000
>                    ifTrue: [Character value: AllProcessInterruptKey]
>                    ifFalse: [AllProcessInterruptKey]]
>
> Now on to making sure that #interruptProcessForLowSpace doesn't come up
> with a process monitor and I think that'll be the last of it, any other
> places I might be missing?
>
> Cheers!
>
> -Boris
>
> --
> +1.604.689.0322
> DeepCove Labs Ltd.
> 4th floor 595 Howe Street
> Vancouver, Canada V6C 2T5
> http://tinyurl.com/r7uw4
>
> [hidden email]
>
> CONFIDENTIALITY NOTICE
>
> This email is intended only for the persons named in the message
> header. Unless otherwise indicated, it contains information that is
> private and confidential. If you have received it in error, please
> notify the sender and delete the entire message including any
> attachments.
>
> Thank you.
>
> > -----Original Message-----
> > From: Boris Popov [[hidden email]]
> > Sent: Tuesday, May 29, 2007 3:18 PM
> > To: Terry Raymond; [hidden email]
> > Subject: RE: [7.5][RTP] Disabling emergency evaluator and process
> monitor?
> >
> > Thanks, I found both easily and was secretly hoping for an AR instead
> ;)
> >
> > Looks like the emergency evaluator can be suppressed with,
> >
> > InputState class>>interruptKeyValue
> >
> > RuntimeSystem isRuntime ifTrue: [^nil].
> > ^InterruptKey < 0
> >     ifTrue: [InterruptKey negated]
> >     ifFalse: [InterruptKey < 16r20000
> >                ifTrue: [Character value: InterruptKey]
> >                ifFalse: [InterruptKey]].
> >
> > but ProcessMonitorClient seems to be wired in much tighter and
> whatever
> > overrides I come up I don't want to have to maintain for long. Just
> > suggesting that both should not be available in the runtime, that's
> all.
> >
> > -Boris
> >
> > --
> > +1.604.689.0322
> > DeepCove Labs Ltd.
> > 4th floor 595 Howe Street
> > Vancouver, Canada V6C 2T5
> > http://tinyurl.com/r7uw4
> >
> > [hidden email]
> >
> > CONFIDENTIALITY NOTICE
> >
> > This email is intended only for the persons named in the message
> > header. Unless otherwise indicated, it contains information that is
> > private and confidential. If you have received it in error, please
> > notify the sender and delete the entire message including any
> > attachments.
> >
> > Thank you.
> >
> > > -----Original Message-----
> > > From: Terry Raymond [[hidden email]]
> > > Sent: Tuesday, May 29, 2007 3:08 PM
> > > To: Boris Popov; [hidden email]
> > > Subject: RE: [7.5][RTP] Disabling emergency evaluator and process
> > monitor?
> > >
> > > Boris
> > >
> > > The code that activates them is in
> > > EventSensor>>keyAt:character:alternative:down:.
> > >
> > > Terry
> > >
> > > ===========================================================
> > > Terry Raymond
> > > Crafted Smalltalk
> > > 80 Lazywood Ln.
> > > Tiverton, RI  02878
> > > (401) 624-4517      [hidden email]
> > > <http://www.craftedsmalltalk.com>
> > > ===========================================================
> > >
> > > > -----Original Message-----
> > > > From: Boris Popov [[hidden email]]
> > > > Sent: Tuesday, May 29, 2007 5:24 PM
> > > > To: [hidden email]
> > > > Subject: [7.5][RTP] Disabling emergency evaluator and process
> > monitor?
> > > >
> > > > In our RTP'ed runtimes hitting Ctrl-Y or walking into an
> > out-of-memory
> > > > condition results in these two tools that have no place in built
> > > > applications IMHO. I'd noticed the 'Install emergency evaluator as
> > > > dialog' setting in RTP, but it didn't seem to have any noticeable
> > effect
> > > > and I didn't see anything relating to process monitor at all.
> Should
> > > > these two be disabled in a runtime by default? Anyone have a patch
> > to
> > > > disable them before I go on a safari myself?
> > > >
> > > > -Boris
> > > >
> > > > --
> > > > +1.604.689.0322
> > > > DeepCove Labs Ltd.
> > > > 4th floor 595 Howe Street
> > > > Vancouver, Canada V6C 2T5
> > > > http://tinyurl.com/r7uw4
> > > >
> > > > [hidden email]
> > > >
> > > > CONFIDENTIALITY NOTICE
> > > >
> > > > This email is intended only for the persons named in the message
> > > > header. Unless otherwise indicated, it contains information that
> is
> > > > private and confidential. If you have received it in error, please
> > > > notify the sender and delete the entire message including any
> > > > attachments.
> > > >
> > > > Thank you.

All that makes sense, thanks for the hints. Wouldn't you agree that both should be disabled in packaged runtime by default? I bet a lot of applications out there are subject to this unless people had suppressed both explicitly, in which case the default would save everyone a bit of running around as well.

Cheers!

-Boris
(Sent from a BlackBerry)

----- Original Message -----
From: Joachim Geidel <[hidden email]>
To: Boris Popov
Cc: [hidden email] <[hidden email]>
Sent: Sat Jun 02 05:36:09 2007
Subject: Re: [7.5][RTP] Disabling emergency evaluator and process monitor?

Hi Boris,

Boris Popov schrieb am 30.05.2007 00:38:
> Oh, Ctrl+\ can also be fixed the same way with,
>
> allProcessInterruptKey
>   RuntimeSystem isRuntime ifTrue: [^nil].
>   AllProcessInterruptKey ifNil: [self initializeProcessInterrupt].
>   ^AllProcessInterruptKey < 0
>       ifTrue: [AllProcessInterruptKey negated]
>       ifFalse: [AllProcessInterruptKey < 16r20000
>                    ifTrue: [Character value: AllProcessInterruptKey]
>                    ifFalse: [AllProcessInterruptKey]]

It's not necessary to modify the code. We simply set the special key
values (interruptKeyValue, allProcessInterruptKey, warpToLauncherKey) in
InputState to 0 in runtime images (somewhere in the startup of the
Subsystem for our application). I am not aware of a way to enter a zero
character, and we never had any problems with that.

> Now on to making sure that #interruptProcessForLowSpace doesn't come up
> with a process monitor and I think that'll be the last of it, any other
> places I might be missing?

We found that the best way to install a custom handler for low space
emergencies is the MemoryPolicy. We are using our own subclass for
various reasons, so the simplest thing to do was override the method
emergencyLowSpaceAction. Our way of dealing with low space emergencies
is to programmatically close one of the inactive open windows (if there
is one), run another garbage collection, and proceed. Another option
would be to alter the memoryUpperBound, if this is the wall which the
application hits, and retry allocating another OldSpace segment. Or try
to empty any caches of your application, run a garbage collection, and
proceed.

This runs in the LowSpaceProcess, which is a high priority process
waiting for low space situations. Anything you do in the LowSpaceProcess
can occur at an arbitrary time, so you should make sure that it doesn't
conflict with what your application is doing. E.g., opening a dialog
from the LowSpaceProcess can be tricky - you must make sure that other
non-system processes don't resume when the dialog's WindowManager
process takes control (that can be done using "Processor
pauseUserProcesses" and "Processor proceedUserProcesses" after closing
the dialog), and that the dialog is running at the right priority.

HTH,
Joachim Geidel

Yeah, getting this default in runtime would be great. Even if it is
fixable, the reality is that in most projects there are so many issues
to deal with that stuff like this is never done. Cincom should do it
for all of us!

Runar

On 6/2/07, Boris Popov <[hidden email]> wrote:

I bet a lot of
applications out there are subject to this unless people had suppressed both
explicitly, in which case the default would save everyone a bit of running
around as well.

---

From: Alan Knight [mailto:[hidden email]]
Sent: June 5, 2007 6:14 AM
To: Runar Jordahl; Boris Popov
Cc: [hidden email]; [hidden email]
Subject: Re: [7.5][RTP] Disabling emergency evaluator and process monitor?

Yes, clearly it should. Created ARs 52333 and 52334 for these.

At 12:49 PM 6/3/2007, Runar Jordahl wrote:

Yeah, getting this default in runtime would be great. Even if it is
fixable, the reality is that in most projects there are so many issues
to deal with that stuff like this is never done. Cincom should do it
for all of us!

Runar

On 6/2/07, Boris Popov <[hidden email]> wrote:

I bet a lot of
applications out there are subject to this unless people had suppressed both
explicitly, in which case the default would save everyone a bit of running
around as well.

--

Alan Knight [|], Cincom Smalltalk Development

[hidden email]

[hidden email]

http://www.cincom.com/smalltalk

"Ideas are a dime a dozen. It's follow through that's hard to come by" - Stephen Chatman