Re: Sending an interrupt to the frontend?
- To: mathgroup at smc.vnet.net
- Subject: [mg127270] Re: Sending an interrupt to the frontend?
- From: Yves Klett <yves.klett at googlemail.com>
- Date: Thu, 12 Jul 2012 04:59:05 -0400 (EDT)
- Delivered-to: email@example.com
- Delivered-to: firstname.lastname@example.org
- Delivered-to: email@example.com
- References: <firstname.lastname@example.org>
In earlier incarnations, the kernel would show up as a separate entry in the taskbar (on Win XP, that was), which made it very convenient to kill. I kind of miss that behaviour (when things go wrong repeatedly). Regards, Yves Am 11.07.2012 08:18, schrieb John Fultz: > It would be nice if the front end were more responsive in these cases (says the > guy who would be responsible for making it happen). In the mean time, one thing > which usually works pretty well is to kill the MathKernel process. Doing so > will typically leave your front end intact and make it responsive again. > > You can do this pretty easily from the Activity Monitor in MacOS, or the Task > Manager (looking at the Processes tab...*not* the Applications tab) in Windows. > > Sincerely, > > John Fultz > jfultz at wolfram.com > User Interface Group > Wolfram Research, Inc. > > > On Tue, 10 Jul 2012 00:40:50 -0400 (EDT), W Craig Carter wrote: >> >> Hello Mathgroup, >> >> This is a question about frozen frontend behavior. >> >> In development stages, one of my frequent mistakes is to send the >> frontend something that takes forever to dynamically update---at least >> that is what I believe what is happening for most of the "freezing" >> occurrences. For MacOs, this is often signaled by a "Formatting >> Notebook Contents" window. >> >> I wonder if anyone has found a method to send the front end a message to >> stop dynamically updating while in an unresponsive state? I've various >> versions of kill -s signal (i.e., signal = INT) from a terminal in >> MacOSx, but never with success. >> >> I suppose that having the front end query the operating system for >> interrupt requests would create a lot of overhead. However, I wonder if >> a method to force the frontend to make an operating system query with a >> user-specified time interval might be possible? >> >> W Craig Carter > > >