CnPack Forum - Powered by Discuz! Board

Subject: Uses Cleaner wizard - out of handles error for larger project [Print This Page]

Author: ajayrp Time: 2015-10-1 21:22 Subject: Uses Cleaner wizard - out of handles error for larger project

I am getting "out of handles" error & IDE hangs, when I try to use the "Uses Cleaner" wizard on my Delphi 2007 project having 3266 files.
However, as an alternative, I can open a handful of files in IDE and run this wizard with limited option to fix files currently opened in IDE.

As the number of files in my project are very large, I can not repeat the alternative way. Can someone tell me, how to fix larger number of Delphi files in a single run?

My environment details are:
CN Pack Version Used: 1.0.7.754 Build 2015.08.15
IDE: Delphi 2007
Operating System: Windows 7 (64 bit) with 8 GB RAM
Number of files in a Delphi project: 3266

Thanks in advance.

[ Last edited by ajayrp at 2015-10-1 21:23 ]

Author: Passion Time: 2015-10-2 21:52

How Large the Project.

We'll consider how to optimize the clean action.

Could you tell us when did the "Out of Handle" occurs? After click "Process" Button in Dialog or click "Clean" Button in Result Dialog?

If a snapshot can be provided, it will help much.

Author: ajayrp Time: 2015-10-5 13:08

Thanks for your reply.
Please find the attached PDF document with detailed steps & screenshots to reproduce this issue.

Attachment: [How to reporduce] UsesCleanerWizard_OutOfHandles.pdf (2015-10-5 13:08, 275.97 K) / Download count 626
http://bbs.cnpack.org/attachment.php?aid=1026

Author: Passion Time: 2015-10-13 09:42

Thanks.

Before we do the clean, we call IDE's API to build the project to get all latest dcus. It seems Out-of-Resource when calling the building API. There's no other good ways to call building, I'll do some investigation more.

Author: ajayrp Time: 2015-10-14 21:16

Thanks for looking in to it.

Actually, I am using below approach - but it is a bit mechanical, painstaking and time consuming. A better workaround is also welcome.
1. Open few files in IDE
2. Run the wizard on opened files
3. Save changes
4. Repeat above steps for next set of files

Thanks again.

Author: Passion Time: 2015-10-15 00:21

Now I do some optimization but still possible out-of-resource when do the processing after get check results. I'll build a new nightly-build version for testing.

Author: Passion Time: 2015-10-15 09:41

The new nightly-build version 787 is available at http://www.cnpack.org/downbuilds.php

Please help to download and verify it? If more problem occurs, please tell us.

Author: ajayrp Time: 2015-10-15 15:23

Thanks for your continuous efforts in providing resolution to this issue.

I tested version 787, but no luck. It raised an "access violation in vcldesigner100.bpl" and then raised same earlier errors: "Code 1158" & "Not enough times available".

Author: Passion Time: 2015-10-16 14:20

Seems very difficult. I'll build a debug version 789 for testing, could you help us to capture the log?

Author: Passion Time: 2015-10-16 14:34

789 debug version is ready. When run Delphi after installation, CnDebugViewer will popup and record the log. After bug occured, please stop CnDebugViewer and save the log to a xml file and send to me?

Thanks.

Author: ajayrp Time: 2015-10-16 16:21

Could you please locate me the 789 build. It is not available at: http://www.cnpack.org/downbuilds.php

Thanks.

Author: Passion Time: 2015-10-17 14:07

At the bottom of the page. or http://www.cnpack.org/downbuilds.php?kind=debug&lang=en

Author: ajayrp Time: 2015-10-19 19:20

The log generated by CnDebugViewer has some critical information like: project structure, source code files names, etc.
Due to some restrictions at our end, I cannot send out the log as is. Is there any way to generate thelog excluding this information?

BTW, When the access violation in vcldesigner100.bpl occurred the last log printed was:

[Copy to clipboard]

CODE:

.

.

.

<CnMsgs>

   <Level>3</Level>

   <Indent>0</Indent>

   <ProcessId>4052</ProcessId>

   <ThreadId>2496</ThreadId>

   <Msg>AppEventNotify: aeDeactivate</Msg>

   <MsgType>cmtInformation</MsgType>

   <TimeStampType>ttDateTime</TimeStampType>

   <MsgDateTime>2015-10-19T15:32:17.054</MsgDateTime>

   <MsgTickCount>0</MsgTickCount>

   <Bookmarked>0</Bookmarked>

</CnMsgs>

  </TCnMsgStore>

</data>

[ Last edited by ajayrp at 2015-10-19 19:28 ]

Author: Passion Time: 2015-10-20 09:49

This one log is the last one but not useful. Could you find the "OS Exception' item in CnDebugViewer? Its items nearby maybe show the error call stack.

Welcome to CnPack Forum (http://bbs.cnpack.org/)