#1  
Old 16th September 2016, 12:51 AM
gsachs gsachs is offline
Member
 
Join Date: Oct 2008
Posts: 53
Default LineTimer blocks OpenDialog

On my application I want to profile only a single method. That method is called after a file is read in and processed.
When the OpenDialog occurs, it shows normally folders and files contained in that folders. With LineTimer it does not, see attached jpg.
It seems that Linetimes slows down even routines that not declared as profiling target.
Is there a way to tell Linetimer to keep hands off of unselected routines ?

Regards
Gerhard Sachs
Attached Images
File Type: jpg Profiler LineTimer.JPG (37.2 KB, 3 views)
  #2  
Old 16th September 2016, 01:11 AM
Eivind Bakkestuen [NDD]
 
Posts: n/a
Default Re: LineTimer blocks OpenDialog

> On my application I want to profile only a single method. That method
> is called after a file is read in and processed.
> When the OpenDialog occurs, it shows normally folders and files
> contained in that folders. With LineTimer it does not, see attached
> jpg.


It appears the folder is a network folder? Can files be found in local
folders? If so, it may be a permission problem (is the testing being
performed as a different user as compared to running standalone).

> It seems that Linetimes slows down even routines that not declared as
> profiling target.
> Is there a way to tell Linetimer to keep hands off of unselected
> routines ?


Is this extra info on the above, or a second, unrelated issue?

--
Eivind Bakkestuen [NDD]
  #3  
Old 16th September 2016, 06:32 PM
Stefan Paege
 
Posts: n/a
Default Re: LineTimer blocks OpenDialog

gsachs wrote:

>
> On my application I want to profile only a single method. That method
> is called after a file is read in and processed.
> When the OpenDialog occurs, it shows normally folders and files
> contained in that folders. With LineTimer it does not, see attached


Maybe related to this thread:

"MethodTimer V. 1.59 "hangs" my app when calling TOpenDialog.Execute"

started last January in this group.


Regards
Stefan (GMT+2)
  #4  
Old 17th September 2016, 02:04 AM
gsachs gsachs is offline
Member
 
Join Date: Oct 2008
Posts: 53
Default

The OpenDialog behaves the same on local or network drives. I can select drives at will but the list below stays empty. The taskmanager shows a CPU load of 11%. When I type a file name and click the Open button, the systems seems to stop there, although I can drag around the dialogbox fluently and the CPU load stays at 11%. After about 30 seconds I can continue and finally extract the profiling times.

There is no permission issue, the same exe with the same paths works smoothly without profiler.

My question is : why does the OpenDialog respond to the profiler although I marked only one method for profiling and that method is not yet called at the time when the dialogbox pops up ?

The Thread "MethodTimer V. 1.59 "hangs" my app when calling TOpenDialog.Execute" talks probably about the same problem, but gives no solution.
  #5  
Old 17th September 2016, 10:47 AM
Thorsten Engler [NDA]
 
Posts: n/a
Default Re: LineTimer blocks OpenDialog

The "open dialog" initializes the shell.

Essentially it loads everything that's normally living in explorer.exe,
including countless registered shell extension dll's from third parties, which
may start additional threads and do who-knows-what, into your process. Also, it
initializes COM in a particular way, and if COM is already initialized
differently for the current thread, Bad Things[tm] happen.

gsachs wrote:

>
> The OpenDialog behaves the same on local or network drives. I can select
> drives at will but the list below stays empty. The taskmanager shows a
> CPU load of 11%. When I type a file name and click the Open button, the
> systems seems to stop there, although I can drag around the dialogbox
> fluently and the CPU load stays at 11%. After about 30 seconds I can
> continue and finally extract the profiling times.
>
> There is no permission issue, the same exe with the same paths works
> smoothly without profiler.
>
> My question is : why does the OpenDialog respond to the profiler
> although I marked only one method for profiling and that method is not
> yet called at the time when the dialogbox pops up ?
>
> The Thread "MethodTimer V. 1.59 "hangs" my app when calling
> TOpenDialog.Execute" talks probably about the same problem, but gives no
> solution.


  #6  
Old 19th September 2016, 07:56 PM
gsachs gsachs is offline
Member
 
Join Date: Oct 2008
Posts: 53
Default

I wanted to profile a mathematical evaluation that is part of a larger software. After I changed it into a separate Exe with no filehandling, it worked much better. This time I was able to find a bottleneck in the software. Changing that gave me about 15% more execution speed, so LineTimer has proven a valuable tool. On the other hand it means applications with filehandling are hard or even impossible to profile.
From my side this case can be closed.
Regards
Gerhard Sachs


Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
nxServer blocks new sessions after undefined error j.halder nexusdb.public.support 1 19th November 2013 08:21 AM
Windows XP Firewall blocks Nexus John Jefkins nexusdb.public.support 1 2nd April 2007 09:38 PM
Block number is either < 0, or >= number of blocks in file [$3C31/15409] Pierre Demers nexusdb.public.support 3 15th April 2006 12:41 AM
Multiple SQL Statement Blocks Michael Wandrey nexusdb.public.support.sql 15 12th June 2004 12:46 PM
Reading values from encryptionengine blocks Tor Tveitane nexusdb.public.support 4 23rd September 2003 12:51 AM


All times are GMT +11. The time now is 03:59 PM.


Powered by vBulletin® Version 3.6.8
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.