public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Machine very sluggish while compiling
Date: Tue, 06 Dec 2011 10:39:00 -0000	[thread overview]
Message-ID: <20111206103834.GL12518@calimero.vinschen.de> (raw)
In-Reply-To: <4EDD44E0.7070701@cornell.edu>

On Dec  5 17:25, Ken Brown wrote:
> On 12/4/2011 5:06 AM, Corinna Vinschen wrote:
> >Anyway, stoppping the PCA service and setting its start mode to "Manual"
> >does the trick for me.
> 
> It does the trick for me too.  For a long time I've been unable to
> build emacs using cygport's default for parallel make (-j5 because I
> have 4 cores).  When I did this, I would either have the computer
> freeze (and I would have to shut it down with the power button) or
> else I would get a BSOD.
> 
> Since stopping PCA, the problem seems to be gone.

In the meantime I found another way how to avoid this problem.

Here's an excerpt from the MSDN man page of AssignProcessToJobObject:

  If the process is being monitored by the Program Compatibility
  Assistant (PCA), it is placed into a compatibility job. Therefore, the
  process must be created using CREATE_BREAKAWAY_FROM_JOB before it can
  be placed in another job. Alternatively, you can embed an application
  manifest that specifies a User Account Control (UAC) level in your
  application and PCA will not add the process to the compatibility job.

So, what I did was to change Cygwin locally to add the
CREATE_BREAKAWAY_FROM_JOB flag to the CreateProcess call when execing a
process.  With this change, I had no problems with PCA anymore.

I also tried to use an "asInvoker" side-by-side manifest for mintty, but
I had no luck with it.  PCA still wasted memory and CPU.

So I'm wondering if we should simply add the CREATE_BREAKAWAY_FROM_JOB
flag to our CreateProcess calls and be done with it.  As far as I can
see, and from what MSDN claims, there should be no problem doing that.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

  reply	other threads:[~2011-12-06 10:39 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-25  4:07 Ryan Johnson
2011-11-25  4:17 ` Mike
2011-11-25  7:22   ` Ryan Johnson
2011-11-25 15:48 ` Spiro Trikaliotis
2011-12-04  7:55   ` Ryan Johnson
2011-12-04 10:07     ` Corinna Vinschen
2011-12-05 22:25       ` Ken Brown
2011-12-06 10:39         ` Corinna Vinschen [this message]
2011-12-08 11:18       ` Robert Miles
2011-12-08 13:15         ` Ryan Johnson
2011-12-04 19:29     ` Christopher Faylor
     [not found]       ` <4EDBD5A5.2000707@cs.utoronto.ca>
2011-12-04 20:23         ` Ryan Johnson
2011-12-06 17:39 ` Andrew Schulman
2011-12-07  5:23   ` Mike

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20111206103834.GL12518@calimero.vinschen.de \
    --to=corinna-cygwin@cygwin.com \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).