public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: Jack <ostroffjh@sbcglobal.net>
To: cygwin-xfree@cygwin.com
Subject: Re: Xwin 1.14.2 (64 bit) extreme memory page faulting
Date: Thu, 03 Oct 2013 18:29:00 -0000	[thread overview]
Message-ID: <1380824987.1265.8@ffortso4> (raw)
In-Reply-To: <CACoZoo38cLb1eH2h3faf3que+wDqED+h9fiBuy0XnKkCHM96WA@mail.gmail.com> (from	erik.soderquist@gmail.com on Thu Oct  3 12:46:27 2013)

On 2013.10.03 12:46, Erik Soderquist wrote:
> <snip>
> > I just fired up a 64-bit Ubuntu VM I had laying around, installed  
> firefox,
> > and tunneled it to cygwin64/X on my win7-64 machine. X isn't even  
> visible in
> > the task manager when I sort descending by PF delta, CPU, or  
> memory. This in
> > spite of having half a dozen tabs with content (including ads, an  
> html5
> > game, and a youtube video playing).
> >
> > Opening a couple dozen more empty tabs brought PFdelta up to the  
> ~7k range,
> > but the rate dropped back to ~0 as soon as the dust settled. Typing  
> remains
> > fully responsive, and I'm officially out of ideas.
> >
> >
> > Ryan
> 
> That is the kind of responsiveness I expect, and what other people
> I've discussed this with experience, which is why I think it is
> something unusual in my setup or environment...  Unfortunately, I'm
> currently unable to find it myself, and can reliably reproduce the
> issue even in a virgin environment.
> 
> So far, the only common factors (that I see) across each of these has
> been my Linux host, (CentOS 5.8 at present) and my various
> tabs/accounts.  However, I am at a complete loss as to even guess at
> how these could affect page faulting on the X server.
> 
> For reference: on the Linux host, when the Windows host is
> experiencing these page faults, the Linux host is reporting 20-30% CPU
> usage overall, no swap usage.

Similar, to but different from Larry's suggestion, can you install  
Firefox on CentOS using the installer from Firefox itself, and not the  
distro version?  I can imagine it could be something about flags or  
settings they used when compiling it.

Jack
--
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/


  parent reply	other threads:[~2013-10-03 18:29 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
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 [this message]
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=1380824987.1265.8@ffortso4 \
    --to=ostroffjh@sbcglobal.net \
    --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).