POST
|
Hello Jeff! Thanks a lot for your attention! Well, the area is only 50x50 meter means it is small enough to run the tool. The other parameters like sky size, coordinate system, zenith and azimuth division etc. were kept as default. As regards using spawnV, please note that I am using VB.NET as the language and I have tried all possible options to destroy the GP once it goes out of scope. But it did not work. Thanks, Imran
... View more
05-16-2011
02:13 AM
|
0
|
0
|
422
|
POST
|
Hello kenbuja!! Thanks for your attention! I have applied your geoprocessing sub but still no luck, sorry to say. I am using point solar radiation tool and perhaps this particular geoprocessing tool has some bugs (Just a wild guess). I would highly appreciate if you have any other idea. I would also like to take attention from ESRI guys in this regards. Thanks, Imran
... View more
04-14-2011
01:20 AM
|
0
|
0
|
422
|
POST
|
Hello Stefan! Yes, I tried. For example: comReleaser.ReleaseCOMObject(GP) GP = Nothing GC.Collect() GC.WaitForPendingFinalizers() But it did not work. Any other idea?? Thanks, Imran
... View more
04-13-2011
06:42 AM
|
0
|
0
|
422
|
POST
|
I am using the point solar radiation geoprocessing tool in a loop of around 100000 times. I have noticed that the virtual memory increases tremendously after each loop. Thus after a certain time the program crashes when the virtual memory gets its maximum limit. The problem seems that the geoprocessing tool object is unable to release the resources once it goes out of scope. Please note that I have tried almost all possible options to destroy the object (geoprocessing tool) once it goes out of scope. For example, I have tried AOUninitialize.Shutdown()method, ComReleaser.ReleaseCOMObject () method, Marshal.ReleaseComObject() method, Garbage collector etc. but none of those could solve the problem. Besides, I have tried to execute the geoprocessing tool separately with managed and unmanaged assembly to observe any noticeable changes in the virtual memory consumption. But, unfortunately nothing good happened. Finally, I have tried to run the code specific for executing the point solar radiation tool in a separate subroutine so that in each loop the program jump in to that separate sub, execute the geoprocessing tool and exit the sub. The idea was, with the exit of sub, the system should release all the resources and allocated memory. But again it failed. now my queries are: 1. Is there any other way to solve this problem 2. Is this a serious bug still alive in the arcobjects 3. If it is a bug then how long the user have to wait for a solution.
... View more
04-13-2011
05:08 AM
|
0
|
7
|
3314
|
Online Status |
Offline
|
Date Last Visited |
11-11-2020
02:23 AM
|