Regular temporary freezing of the UI after switching to x64

[GoogleCodeExporter]

What steps will reproduce the problem?
1. open pyscripter
2. work as usual
3. profit

What is the expected output? What do you see instead?

I expect a responsive UI; instead, it frequently hangs for substantial amounts 
of time; not just a stutter, but up to 20 seconds, I would guess. Not enough 
for windows to report it as not responding, but the whole interface might as 
well have been a bitmap. All other programs remain responsive.

What version of the product are you using? On what operating system?

2.5.3.0 x64, win7 64bit

Please provide any additional information below.

Never had this problem with 32 bit python and the 32 bit version of pyscripter; 
it appeared after my recent upgrade to 64 bit.

Another point of note may be that I am doing a lot of multiprocessing at the 
moment, in addition to keeping several pyscripter windows upen with the -N 
command line arg; not sure if this could be related, but these changes have 
coincided with my switch to 64 bit; not sure if the problem is exclusive to 
those situations, but I will try to find out.

Original issue reported on code.google.com by hoogendo...@gmail.com on 6 Aug 2012 at 10:50

• Merged into: #722

[GoogleCodeExporter]

Update: just happened again; only a single pyscripter instance open, no 
multiprocessing. I should note that I use the remote python engine; I should 
create a seperate issue for this perhaps, but the internal engine does not work 
(did work under 32 bit). The internal engine starts up fine, but importing 
numpy, for instance, fails with 'ImportError: DLL load failed: %1 is not a 
valid Win32 application.'. The same seem to apply to any other import that 
depends on DLL's.

The latter is probably due to something being wrong with my path, or other 
issues with my previous 32bit install, I suspect. I dont much care for the 
internal engine problem, but just mentioning it in case there could be a 
relation to the issue I am experiencing with the remote engine.

Original comment by hoogendo...@gmail.com on 6 Aug 2012 at 11:58

[GoogleCodeExporter]

Ive got a new clue; I have been starting pyscripter through a shortcut with -N 
as a default option. If i start it through the default start menu shortcut, the 
problem might disappear; at least it has been absent for at least an hour now, 
which is exceptional.

Original comment by hoogendo...@gmail.com on 6 Aug 2012 at 3:21

[GoogleCodeExporter]

Thanks for the update.  Please let me know if the error persists. 

Original comment by pyscripter on 8 Aug 2012 at 1:29

[GoogleCodeExporter]

Found out something significant: when it freezes, everything except the win32 
parts of the window are unresponsive. So I can still change the size of the 
outer window (but not of the inner partitions). But when I do resize the 
window, it snaps out of its coma! Not only useful for me, but it might also 
help diagnose the problem.

By the way, the excellent code completion that pyscripter enjoys, also does not 
work under x64; I suppose this is strongly related to the internal engine not 
working, and I suppose a similar mechanism is used in the code inspection; 
loading numpy in an internal engine (which fails), after which is falls back to 
static code inspection. (meaning you miss half of numpys documentation). I 
still think this must be some instllation problem; but I tried uninstalling 
both x32 and x64 pyscripter, and reinstalling, but that didnt change a thing.

Original comment by hoogendo...@gmail.com on 9 Aug 2012 at 1:55

[GoogleCodeExporter]

Another update:

Just migrated to my new macbook pro retina, and two observations:

This is obviously a clean install (win7); latest version of EPD adademic python 
2.7 64 bit. But 64bit pyscripter has the same issues I reported earlier. That 
is, function help is incomplete; numpy.array or numpy.concatenate, for 
instance, do not show up in the list (even when added to the special packages 
list). Also, the internal python engine fails to load external libs, so 
importing numy internally fails. I have a suspicion the freezing will happen as 
well, but ill come back to that later

The UI is quite hard to use on retina. Lines of text in the IDE options more or 
less disappear in their textboxes, which seem to have a hardcoded pixel size. 
Anyway, not that I expect this to be much of a priority, but thought id mention.

Original comment by hoogendo...@gmail.com on 12 Sep 2012 at 12:21

[GoogleCodeExporter]

Correction: after installing a slew of windows updates, the way it deals with 
DPI scaling has changed quite radically; after this, pyscripter looks fine; the 
more pressing issues persist though.

Original comment by hoogendo...@gmail.com on 12 Sep 2012 at 1:51

[GoogleCodeExporter]

Original comment by pyscripter on 23 Mar 2015 at 2:54

• Changed state: Duplicate