De-activating EurakaLog on a project causes BDS.exe 100% CPU

[micronav]

Hi,

We are using CodeGear C++Builder 2007 and EurekaLog 6.0.21 RC 3 Pro.

When you De-Activate EurekaLog from a project the bds.exe process goes to %100 cpu. You have you shutdown and restart Builder to stop it.

Regards,
Micronav.

[Alex]

Hi, micronav.

I can not confirm this issue right now.
Can you do a little experiments?
Does this happens before, with other versions of EurekaLog? Or on another machine?
I've meet some situations with 100% load of BDS, but that was IDE bugs (unfortunately, I don't remember details now :( ).

You can also use Process Explorer tool to open BDS.exe properties and see its threads, to detect which one is taking CPU. Try to see its call stack.

[micronav]

Hi Alex,

I have tested:

6.0.10 Pro
6.0.16 Pro
6.0.20 Pro
and
6.0.21 Pro RC3

And they all do the same thing. I have also tried this on another machine and it still happens.

When I look using process explorer the thread that is taking 100% CPU is:

rtl100.bpl!System+0x20

The callstack varies depending on when you catch it but it is always GetModuleFileName. Occasionally CExceptionExpert appears in the list, as you can see below.

ntkrnlpa.exe+0x6e9ab
ntkrnlpa.exe!MmIsDriverVerifying+0xbb0
hal.dll+0x2ef2
rtl100.bpl!System+0x16
CExceptionExpert11.bpl!EOption+0x25
rtl100.bpl!Classes+0x20f
rtl100.bpl!System+0x4a
kernel32.dll!GetModuleFileNameA+0x1ba

Hope this helps,

Ken.

[Alex]

Hi,

Great thanks for your valuable feedback!
I'll try to analyze this situation with the new info.

[Alex]

Hi,

I've managed to find a source for this problem.
There should be a new RC soon, fixing this issue. I'll drop a note here, when it is ready for download.

Thanks again for your valuable feedback :)

[micronav]

Your welcome! :)

I look forward to the RC.

btw. the big problem for us is this one:

http://news.eurekalog.com/showthread.php?t=2385

If there's anything I can do to help you fix it let me know.

Kind regards,

Ken.

[Alex]

Hi,

There is a new RC 4 available. Can you retest this issue with it?

[micronav]

Alex,

I can confirm that the issue has been fixed.

Thank you :)

[Alex]

Hi,

Ok, great :)

Sorry, but your other issue is still unfinished.