public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: Ryan Johnson <ryan.johnson@cs.utoronto.ca>
To: cygwin-xfree@cygwin.com
Subject: Re: Xwin 1.14.2 (64 bit) extreme memory page faulting
Date: Thu, 03 Oct 2013 14:01:00 -0000	[thread overview]
Message-ID: <524D78AF.3040607@cs.utoronto.ca> (raw)
In-Reply-To: <CACoZoo2VtsGHdJ=hyfO0S=1ku5z0Mv51MFoaoJGGnPZdYGigpw@mail.gmail.com>

On 02/10/2013 7:55 PM, Erik Soderquist wrote:
> On Wed, Oct 2, 2013 at 6:51 PM, Ryan Johnson
> <ryan.johnson@cs.utoronto.ca> wrote:
>> I doubt it's an X-server code issue. You tried it on too many machines with
>> problems, and too many other people aren't spamming the list about this,
>> which suggests it's something on your side (like BLODA). Further, the only
>> cygwin bug I've known to cause lots of paging was plugged months ago (it had
>> to do with sparse executable files and should have been irrelevant for this
>> situation anyway).
> The only (known) BLODA I have from that list is the McAfee
> A/V-firewall, which I can't remove, but I believe was completely
> disabled by the above described method.
Unfortunately, McAfee is one of the worst offenders in my experience 
[1]. I seriously doubt you can disable it completely from user space, 
given its habits of interposing on device drivers and burrowing into 
other kernel bits [2].

[1] IMO it's a cure that's worse than the disease, but that's a rant for 
a different thread.

[2] McAfee actually sued MS for "anticompetitive" behavior a while back, 
after the latter closed a bunch of security loopholes in the kernel that 
virus-writers love but McAfee also depended on (including the interrupt 
dispatch table IIRC).

>> My advice: check out the cygwin FAQ about BLODA, uninstall anything listed
>> there (or install a fresh VM image somewhere without those) and try again.
>> If it's still a problem, somebody more familiar with X than me will have to
>> take over...
>>
> If I can get the authorization for a VM test without A/V, I will and
> the results will be posted here either way.  Thank you for your time
> in looking at this.
Good luck!

Ryan


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


  reply	other threads:[~2013-10-03 14:01 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-02 18:50 Erik Soderquist
2013-10-02 22:51 ` Ryan Johnson
2013-10-02 23:55   ` Erik Soderquist
2013-10-03 14:01     ` Ryan Johnson [this message]
2013-10-03 15:44       ` Erik Soderquist
2013-10-03 16:21         ` Erik Soderquist
2013-10-03 16:27         ` Ryan Johnson
2013-10-03 16:41           ` Ryan Johnson
2013-10-03 16:49             ` Erik Soderquist
2013-10-03 16:46           ` Erik Soderquist
2013-10-03 17:04             ` Larry Hall (Cygwin-X)
2013-10-03 19:22               ` Erik Soderquist
2013-10-03 18:29             ` Jack
2013-10-03 19:27               ` Erik Soderquist
2013-10-03 19:43                 ` Erik Soderquist
2013-10-04 13:21                   ` Erik Soderquist
2013-10-04 14:03                     ` Ryan Johnson
2013-10-04 14:31                       ` Erik Soderquist

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=524D78AF.3040607@cs.utoronto.ca \
    --to=ryan.johnson@cs.utoronto.ca \
    --cc=cygwin-xfree@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).