SQL-panel causes 100% CPU and lockup on windows (Was Stability and compatability issues on windows xp)

Hi,
(and sorry for cross-posting, the issue is imo pretty important)

27.09.2015 14:12, I wrote:
[...]
> Besides, I suspect that with some luck the problem might also trigger on
> vista+ when running pgadmin through a remote desktop, although I'm not
> quite sure.

Ok, no need for remote desktop even.
Just reproduced this on windows 7 64-bit easily, although visual effect
is not so striking as on windows xp (probably due to smarter resource
management in newer OS and/or faster computer).
And I've got much more details now.

This is with pgamin 1.20 from official enterprisedb's installer.

Here is how to reproduce. (Procedure valid at least for win xp and 7)
In under 1 minute!

- 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