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: Wed, 02 Oct 2013 22:51:00 -0000 [thread overview] Message-ID: <524CA379.207@cs.utoronto.ca> (raw) In-Reply-To: <CACoZoo0vCM6TeFqeqkAUOPqs5GECZzmFYOzHPh1SOAm1rzuOEA@mail.gmail.com> On 02/10/2013 2:50 PM, Erik Soderquist wrote: > I am currently using the X server on a Windows 7 64 bit host for > Firefox (in particular, occasional terminals too). While everything > works, I am experiencing very severe memory page faulting causing the > graphical interface to appear to hang for several seconds at a time, > and when not appearing hung, responsiveness is very painfully slow, > sometimes to the extent that I will type a paragraph and then sit back > and watch as the graphical interface slowly displays what I typed at a > rate of 1-2 characters per second. Is there really a Firefox build for cygwin/X ? Or are you tunneling from some other machine? > Testing with antivirus and firewall enabled/disabled did not affect > the results. (faq reference > http://x.cygwin.com/docs/faq/cygwin-x-faq.html#poor-performance found > during searches). If antivirus is a problem (as in BLODA), you probably need to uninstall, not just disable. They're usually too lazy to actually remove their hooks when "off" and just (try to) make the hooks become (mostly) no-ops instead. Not saying it's your problem, necessarily, just that merely disabling AV is not enough to rule it out. Also (not necessarily related to this particular problem), cygcheck reports a surprising selection of *nix-like utilities in c:\windows\bin. Whatever they are, they can't be helping. 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). 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... 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/
next prev parent reply other threads:[~2013-10-02 22:51 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 [this message] 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 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=524CA379.207@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: linkBe 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).