Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1Zgza7-00027j-3F for pgadmin-hackers@arkaria.postgresql.org; Tue, 29 Sep 2015 18:24:51 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84) (envelope-from ) id 1Zgza6-0004p6-Lh for pgadmin-hackers@arkaria.postgresql.org; Tue, 29 Sep 2015 18:24:50 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84) (envelope-from ) id 1Zgza5-0004oM-PA; Tue, 29 Sep 2015 18:24:49 +0000 Received: from forward4o.mail.yandex.net ([37.140.190.33]) by magus.postgresql.org with esmtp (Exim 4.84) (envelope-from ) id 1Zgza0-0005kX-IN; Tue, 29 Sep 2015 18:24:46 +0000 Received: from smtp4o.mail.yandex.net (smtp4o.mail.yandex.net [37.140.190.29]) by forward4o.mail.yandex.net (Yandex) with ESMTP id 3C064564145B; Tue, 29 Sep 2015 21:24:43 +0300 (MSK) Received: from smtp4o.mail.yandex.net (localhost [127.0.0.1]) by smtp4o.mail.yandex.net (Yandex) with ESMTP id D3DAB2320173; Tue, 29 Sep 2015 21:24:42 +0300 (MSK) Received: by smtp4o.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id 2DUP7aaYJ3-OgO0kiYq; Tue, 29 Sep 2015 21:24:42 +0300 (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (Client certificate not present) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1443551082; bh=PoGUBZ7jJ5cx/AwiAuP93xBHbBYbHP5sJ7JaKP5SWHc=; h=Message-ID:Date:From:User-Agent:MIME-Version:To:Subject: References:In-Reply-To:Content-Type:Content-Transfer-Encoding; b=igBCqYUlgVheJUVIDi62zYGoYOFYvxARWbna53UJ/EfB/7BPxDUlMG6EUVf/4Fd38 Tnzwu43PrXZyL6SXZ8D6I/Wqsr3XwzaomFzPVx1AbtPBoPivUKaS8J54D9jX0DFfJT AG7OvnbeWBBRX2NmnqmXnF3Gz9QNhvtHo7YZskgE= Authentication-Results: smtp4o.mail.yandex.net; dkim=pass header.i=@yandex.ru X-Yandex-ForeignMX: US Message-ID: <560ADB34.6050700@yandex.ru> Date: Tue, 29 Sep 2015 21:40:52 +0300 From: Nikolai Zhubr User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; ru; rv:1.9.1.5) Gecko/20091204 Thunderbird/3.0 MIME-Version: 1.0 To: pgadmin-support@postgresql.org, pgadmin-hackers@postgresql.org Subject: Re: [pgadmin-support] SQL-panel causes 100% CPU and lockup on windows (Was Stability and compatability issues on windows xp) References: <5606F2C8.9010001@yandex.ru> <56070F5A.3070102@yandex.ru> <1674144739.20150927082019@mail.ru> <5607CF32.7030707@yandex.ru> <5609BC61.8030503@yandex.ru> In-Reply-To: <5609BC61.8030503@yandex.ru> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Pg-Spam-Score: -2.7 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgadmin-hackers Precedence: bulk Sender: pgadmin-hackers-owner@postgresql.org Hi, 29.09.2015 1:17, I wrote: [...] > Here is how to reproduce. (Procedure valid at least for win xp and 7) > In under 1 minute! Some more observations. Same problem happens also in function properties window, in the 'Code' tab: - choose some simple (lets say empty) function, open its properties; - click on the 'Code' tab; - place this properties window so that its righthand margin is somewhat beyond the right margin of the monitor, making some part of SQL editor invisible (out of the real screen space); - click to place cursor into the function body and type 'select now()'; - watch the CPU load. So it looks like ctlSQLBox instances are affected, although ctlSQLBox itself seems quite harmless (looking at the code), except for maybe ctlSQLBox::OnPositionStc() about which I've just no idea. And since ctlSQLBox is a direct descendant of a wx class, it looks like maybe it is actually wxwin to blame. So my theory is: -- either ctlSQLBox::OnPositionStc() itself, -- or the underlying wx class (classes). I haven't arranged a development environment yet, but am going to. Thank you, Nikolai > - Aero have to be disabled (on versions that have it). If you can not or > do not want to disable aero for some reason, you might try connecting > via remote desktop instead, it should basically behave very similar, > I've tested it as well. > - start windows task manager and minimize it so it just shows CPU load > within a tray icon. (taskmgr.exe) > - start pgamin as usual, connect to some server, then click on some > database, so that SQL-panel button becomes available. > - open SQL-panel (click the above mentioned button), then move SQL-panel > window in the righthand direction till some part of SQL-editor window > rectangle goes beyond the right border of the screen. Let is stay like > that (partly invisible). Note that I mean exactly SQL-editor window > itself, not additional notepad window that might happen to be located to > the right of SQL-editor. (Or you can just close this notepad to be sure) > - now click into SQL-editor so that you can start typing. > - type just exactly this: 'select now()' then stop, do not touch > anything and watch the CPU load. it should go 100% (50% on dual core, > 25% on quad core) and stick there. > - note: it is critical to put brackets there, otherwise bug is not > triggered, so I'd guess this is related to code highlighting. > - now go to SQL-panel's main menu - select file - select exit. instead > of closing, SQL-panel goes completely unresponsive here. > > I'd be glad to hear some feedback (from windows users) :) > > > Thank you, > Nikolai > >> >> >> Thank you, >> Nikolai > > > -- Sent via pgadmin-hackers mailing list (pgadmin-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgadmin-hackers