ActiveState Community

debug slow to start with php 5.2.6

Posted by daveshaw on 2009-04-20 09:43
OS: Windows 2000 Pro / Server

On my Win 2000 Adv Server it takes ~35 seconds from clicking debug start to pull up the Debug Options page and then another ~35 seconds for the debugger to get to the first line break point.

I am playing with an Intel Core 2 Duo CPU E8200 @ 2.66GHz and 2Gig of RAM.

Any ideas on speeding up the time to Debug Options page and then to first break point?

BTW I am a newbie to this wonderful software so thank you for your considerations and assistance.

re: debug slow to start
toddw | Mon, 2009-04-20 10:25

Which version of Komodo?

If your using Komodo IDE version 5.1.0, there is a known bug that caused debugging slowdowns, which was subsequently fixed with the Komodo IDE 5.1.1 release:
http://downloads.activestate.com/Komodo/releases/

Cheers,
Todd

Thanks Todd. Komodo IDE,
daveshaw | Mon, 2009-04-20 10:30

Thanks Todd.

Komodo IDE, version 5.1.1, build 27706, platform win32-x86.

Any more ideas?

- Dave

re: should not be slow
toddw | Mon, 2009-04-20 10:39

Hi Dave,

I cannot think of any particular reasons why this would be so slow, I've not experienced any slowdowns when launching debugging in Komodo 5.1.1 on Windows XP.

Are there any errors getting logged to Komodo's log files:
http://community.activestate.com/faq/komodo-file-locations#log_files

Is there anything particular with the PHP script your debugging (like being a very large file, located on a network share, etc...)?

Thanks,
Todd

file sizes and logs
daveshaw | Thu, 2009-04-23 11:16

Hello Todd,

Had a couple days off :o).

I am working with some included files, all are under 25Kb in size and there are less than 6 files.

Working with simulate CGI environment, and normal debugging, both perform as mentioned before.

Below are the entries from the error log just created from two runs of the debugger,

C:\Program Files\ActiveState Komodo IDE 5\lib\mozilla\python\komodo\twisted\cred\identity.py:23: DeprecationWarning: the md5 module is deprecated; use hashlib instead
import md5, types, sys, warnings
[2009-04-23 14:13:33,421] [ERROR] KoObserverService:
Traceback (most recent call last):
File "C:\Program Files\ActiveState Komodo IDE 5\lib\mozilla\components\koObserverService.py", line 66, in _getLiveObservers
if not callable(wr) or wr() is not None:
File "C:\Program Files\ActiveState Komodo IDE 5\lib\mozilla\python\xpcom\client\__init__.py", line 528, in __call__
return Component(self._comobj_.QueryReferent(iid)._comobj_, iid)
File "", line 3, in QueryReferent
Exception
[2009-04-23 14:13:33,437] [ERROR] KoObserverService:
Traceback (most recent call last):
File "C:\Program Files\ActiveState Komodo IDE 5\lib\mozilla\components\koObserverService.py", line 66, in _getLiveObservers
if not callable(wr) or wr() is not None:
File "C:\Program Files\ActiveState Komodo IDE 5\lib\mozilla\python\xpcom\client\__init__.py", line 528, in __call__
return Component(self._comobj_.QueryReferent(iid)._comobj_, iid)
File "", line 3, in QueryReferent
Exception

~ Dave

re: error logs
toddw | Thu, 2009-04-23 11:22

Hi Dave,

Thanks for the logs. The logs actually look fine, the above two errors are relatively harmless. On thing I forgot to mention, can you shutdown Komodo after the two debugging runs, this is so the log file is completely flushed, then check the log file again?

Thanks,
Todd

And More
daveshaw | Mon, 2009-04-27 12:56

Hello Todd,

I ran two debug sessions then exited komodo and ran two more sessions. I then checked the log files and they were empty ?

Hope you had a good weekend.

~ Dave

Debugger Settings
daveshaw | Tue, 2009-04-28 14:43

Hey Todd,

I ran the tutorial guestbook.php through the debugger. It took ~20 seconds from pressing F5 for the Debugging Options dialog box to appear, then after I followed the instructions it took ~45 seconds for the debugger to pause at the first break point on line 9.

Is there any setup I have to do for the debugging environment that I missed? Is there a manual section I should read first?

Thanks,

Dave

re: debugger slow to start
toddw | Tue, 2009-04-28 15:20

That really does seem quite strange. Can you try debugging another sample (such as Python or Perl), do these debugger dialogs take forever as well?

There is no setup required for local PHP debugging, it should simply start running/debugging (within a few seconds) after launching the "Debug->Go/Continue" command.

Perl and Python
daveshaw | Tue, 2009-04-28 19:05

I loaded the sample projects for both Perl and Python. Both entered debug mode in a flash. Very satisfying!

However php is still slow.

On a hunch (maybe because I just watched the Matrix again) I ran the PHP Configuration Wizard and selected php-cgi.exe instead of php.exe which I had before. I ran debug again and the Debugging Options window opened in ~7 seconds and once set immediately went into debug mode and I could step through the program.

Thanks for the help.

Dave :o)

re: php slow
toddw | Wed, 2009-04-29 10:45

That is good that the php-cgi is working better.

It may be something to do with the php.ini file, you could try creating an empty php.ini file somewhere and then point Komodo's PHP preferences to use this ini file, then see if debugging is any faster after this change.

Cheers,
Todd

Blank php.ini
daveshaw | Wed, 2009-04-29 11:11

I will give that a try and report back.

~ Dave

The blank php.ini
daveshaw | Sat, 2009-05-02 07:46

There seems to be no difference in speed using a blank php.ini file.

~ Dave

Have the same problem
webfaqtory | Tue, 2009-06-30 09:15

PHP 5.2.9
Komodo version 5.1.4, build 30485
WIN XP 64

Had the same problem. Read this thread and set to debug as php-cgi. Komodo is now running like it used to. 2-3 seconds for the debug dialog and starts debugging instantly.

There does seem to be a problem with using php.exe for the debugger.

John