Method Window Slowness with 13.4/Win 7/Parallels

Douglas von Roeder (6/3/14 4:33PM)
Jeffrey Kain (6/3/14 7:59PM)
Tim Nevels (6/4/14 4:21PM)
Tim Nevels (6/4/14 6:17PM)

Douglas von Roeder (6/3/14 4:33 PM)


I'm using 13.4 and 13.5 on Win 7 w Parallels and am experiencing some
oddities in design and debug mode that are perplexing and frustrating.

The computer is a 15" MacBook Pro with an i7 and 16 GB RAM. I've
up to 4 cores (this model has 8) and up to 2 GB RAM to Windows in
to take those factors out of the equation.

Task Manager indicates that 4D is accessing over 1 GB RAM and the RAM
values in the debugger indicate that min stack space is > 300 K.

1 - when I open the debugger window, the "status bar" at the bottom of
window, for want of a better word, is missing and the bottom window
is a very thin border. This is cosmetic-only but may be indicative.

2 - there's a slight delay between user input (me) and the window
to user input. Type in a few letters quickly and, some times, it
that the computer is typing the text very slowly.
Opt-drag (control drag) and release to copy a block of text requires
patience - there's perhaps a two second lag for that operation.
In design, at times, when I move the cursor in a left to right fashion
front of/above" the method editor, the horizontal scroll bar will

3 - the method editor sometimes flashes.

I've experienced this while using my 27" iMac as a remote display
(just run
a DVI cable from the MBP to the DVI port on the back of the iMac);
when a
standard sized (1920 x 1080) ASUS monitor is attached; and, to a lesser
extent, when using the MBP screen (I haven't tested it with multiple
resolution settings on the MBP but the laptop has two graphics cards
with a
total of 1.5 GB VRAM so it's not a lack of GPU power).

Any suggestions on how to resolve this?

Has anyone experienced this and/or know of a solution?

Thanks in advance.

Douglas von Roeder

Jeffrey Kain (6/3/14 7:59 PM)

I?=80&ocirc;ve got a really similar configuration and haven?=80&ocirc;t had
these issues.

Are you up-to-date on Parallels? I?=80&ocirc;m running 9.0.24229.

Another difference is I?=80&ocirc;m running Windows 8.1, but I was running
Windows 7 on my previous computer (an Air with way less memory) and
didn?=80&ocirc;t have these problems.

On Jun 3, 2014, at 7:33 PM, Douglas von Roeder <dvonroeder@...

color><param>00000,0000,DDEE/param>AAny suggestions on how to resolve

Has anyone experienced this and/or know of a solution?

Tim Nevels (6/4/14 4:21 PM)

On Jun 4, 2014, at 2:24 PM, Douglas von Roeder wrote:

color><param>00000,0000,DDEE/param>AAfter a reboot, I deleted the
folder and ran the installer for 13.4.

Much to my delight, the lag is no longer apparent (that's my version of
"Everything appears to be OK.")

Root cause?
Could have been a problem with how 4D was installed but I don't recall
every happening and my impression is that's rare.
Could it have been the "funky folder"? I experienced this issue 13.4
13.5 . The issue is resolved for 13.4 but I'm still experiencing it
13.5. I'll be doing the 13.5 reinstall later today.
Good news Doug. Didn't somebody suggest doing a 4D reinstall? :-)

I think many problems that are fixed by a re-install of the software
are due to "silent errors". These are errors that occur -- in 4D or in
Windows -- that the programmers don't checks for and thus does not
display a visual error message.

In your case probably a permissions error related to that funky
folder. 4D or Windows tried for a while to access the folder and
couldn't. 4D didn't check for the error condition so no visual error
message was displayed. It would be crazy inefficient if 4D had to
error check every disk access to for valid permissions.

The good thing is you've got it fixed.


Tim Nevels (6/4/14 6:17 PM)

On Jun 4, 2014, at 5:43 PM, Douglas von Roeder wrote:

color><param>00000,0000,DDEE/param>""Good news Doug. Didn't somebody
suggest doing a 4D reinstall? :-)"
Oops - I forgot to thank you.
Thank Microsoft for creating Windows with no real concern for security
that resulted in the god awful world of viruses on Windows, which then
resulted in the bullish*t we all experience now from Microsoft trying
to fix their past mistakes and secretly modifying and changing
permissions on things they "think" could be "bad". And of course it is
all secret because if they told us about all the crazy stuff they are
doing under the hood the virus makers would know too and work around

Or it could be your typical permissions corruption problem that nobody
knows why and or how it occurs.

The good news is the reinstall of 4D uncovered the underlying problem,
which lead to a fix.

The next step would have been the traditional "start over" and wipe
the drive and reinstall Windows from scratch. That seems to fix almost
everything. Thank God you didn't have to do that.


Reply to this message

Summary created 6/5/14 at 3:21PM by Intellex Corporation

Comments welcome at: