DMARC-Filter: OpenDMARC Filter v1.4.2 delorie.com 4BC3rUIs1827465 Authentication-Results: delorie.com; dmarc=pass (p=none dis=none) header.from=cygwin.com Authentication-Results: delorie.com; spf=pass smtp.mailfrom=cygwin.com DKIM-Filter: OpenDKIM Filter v2.11.0 delorie.com 4BC3rUIs1827465 Authentication-Results: delorie.com; dkim=pass (1024-bit key, unprotected) header.d=cygwin.com header.i=@cygwin.com header.a=rsa-sha256 header.s=default header.b=QSu5T4js X-Recipient: archive-cygwin AT delorie DOT com DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 65D9F3858C98 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com; s=default; t=1733975609; bh=kNv+S6Bw1TS9yiDsqcrzyU5RcxY7RsRYT0czLQpYCI8=; h=Date:To:Subject:In-Reply-To:References:List-Id:List-Unsubscribe: List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To: From; b=QSu5T4jslPYigdN94MufqTbJkgGT9i5pnDheZFb8PORkY4X58z6VVHWzhVGB1sm7N mPOWfrKP8eekaIuX/QqaMDyyc9gsIcfkb/DtWv4oH4o1trv0eRoEEMvrx39PoqxX1L PegkJ4LXjTsomAtDrPZi9eDrs8Eic5cGocegFouw= X-Original-To: cygwin AT cygwin DOT com Delivered-To: cygwin AT cygwin DOT com DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org D254A3858D29 ARC-Filter: OpenARC Filter v1.0.0 sourceware.org D254A3858D29 ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1733975585; cv=none; b=L98UXNFm093n0RGy8H78FGNJRaM3Nr9jyrcyQUzW+bljMIa9yrMhJ/PgwoHs5CxZMmIxeii3Q5uefd1LjUlZZuUI6ytI4yhAroC9No4ToAecuQDocVcrtAv+AxLDXVr+TyaiAOP97ZKmniu5HEJFn8huqn+39aCJfF6ii5vRNEs= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1733975585; c=relaxed/simple; bh=iLZU6Kk3u9nDqC88PaFzgD0bsqeAmGfpVHNdQ3uAYog=; h=Date:From:To:Subject:Message-Id:Mime-Version:DKIM-Signature; b=JFW8oSU21sCKT+0JGOPBN+dJGMJXIYnpgt5yRa+jzjs6dfWtneBZM99w3FTLQsiRY7fByIPuH7jufbzNwljQBa2jRjPfytisuG6qJIYEManlTEIuk2xpjmU5NwtUEiC2qSMDxtW7IkFryfgZsCgOaRiAGdkEOn0AnK4DqNG8YQw= ARC-Authentication-Results: i=1; server2.sourceware.org DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org D254A3858D29 Date: Thu, 12 Dec 2024 12:52:59 +0900 To: =?UTF-8?B?5Yev5aSP?= via Cygwin Subject: Re: cpu issue on when using less Message-Id: <20241212125259.b409d444e54b2e69675ee56f@nifty.ne.jp> In-Reply-To: References: X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.30; i686-pc-mingw32) Mime-Version: 1.0 X-BeenThere: cygwin AT cygwin DOT com X-Mailman-Version: 2.1.30 Precedence: list List-Id: General Cygwin discussions and problem reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Takashi Yano via Cygwin Reply-To: Takashi Yano Content-Type: text/plain; charset="utf-8" Errors-To: cygwin-bounces~archive-cygwin=delorie DOT com AT cygwin DOT com Sender: "Cygwin" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by delorie.com id 4BC3rUIs1827465 On Thu, 12 Dec 2024 11:24:40 +0800 凯夏 via Cygwin wrote: > When I use less read from pipe,even i just output a empty new line to less, > the bash running less gets high cpu usage ( picture 1, picture 2 ), and > less itself didn't use many cpu, when i quit less, cpu usage of bash drop > to normal ( picture 3 ) > When I use less read from file,the bash running less gets low cpu usage > How can I debug this? > I post these three snapshot on imgur if you can't see them: > https://imgur.com/a/mDfH8Dl Thanks for the report. Which version of cygwin are you using? -- Takashi Yano -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation: https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple