Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!think.com!mintaka!bloom-beacon!eru!kth.se!cyklop.nada.kth.se!news From: d88-pfo@dront.nada.kth.se (Peter Forsberg) Newsgroups: comp.os.os2.programmer Subject: Re: OS/2 message queues killing processes Message-ID: Date: 21 May 91 20:05:37 GMT References: <1991May21.140334.20170@murdoch.acc.Virginia.EDU> Sender: news@nada.kth.se (Mr News) Organization: Royal Institute of Technology, Stockholm, Sweden Lines: 24 In-reply-to: djm5g@virginia.edu's message of 21 May 91 14:03:34 GMT If I get your problem right it is approximately the following (in summary): You have a PM program, that processes some initialization message (system or user defined, doesn't really matter). If this message processing takes too long time (a few seconds...), you get the "Program not responding..." dialog, which presents you with an option to end the program. If your situation is the one above, the problem probably is that the message processing time is too long. The recommended maximum time for processing any PM message is 1/10 second. If you have work which will take more time (a few seconds), you should create a separate thread to do that work, letting the message processing thread return control to PM. The reason for this is in the design of PM, which cannot pass on several types of messages to other windows until you have finished your message processing. Hope this helps... / Peter -- Peter A. Forsberg Royal Institute of Technology, Stockholm, Sweden. IBM Sweden, Banking & Finance Applications. E-mail: d88-pfo@nada.kth.se #include