TeeCahrt 4.2020.8.28 & 9.16

[HCCKPM_2020]

Good Morning Christopher,

sorry to say that .61 and alos .62 don't work either.
Maybe you can write some logs during the DLL access so I can send you the output?

[Christopher]

Good morning

sorry to say that .61 and alos .62 don't work either.

Maybe you can write some logs during the DLL access so I can send you the output?

That's bad news. We use Git as our source-code repository, and tag all our version releases. This guarantees identity of source-code through different builds. Both the versions above were built from the tag we put on version 4.2020.5.25, one with obfuscation and one without.

If obfuscation is not the problem, and the source-code used for the build is identical to the build you say that works, then I'm afraid I'm out of ideas of how to continue. At this time I can't see how writing logs is going to help us.

We're going to have to come up with another approach; maybe something will come to us over the next few days. Please let us know if you can think of an explanation as to why our Git repository is failing to rebuild an assembly which works.

[Christopher]

Hello,

We're going to have to come up with another approach; maybe something will come to us over the next few days. Please let us know if you can think of an explanation as to why our Git repository is failing to rebuild an assembly which works.

Talking to colleagues here, and they've come up with a couple of useful suggestions which we could try. The first one is to discount the possibility that version 4.2020.5.25 had some code in it that no other version has, and that it is this code which is causing this version to work - an easy way to discount that possibility would be for you to use the version previous to it - for example 4.2020.5.12 and/or 4.2020.4.6.

The second suggestion is to remind you of a question posed by a colleague of mine here, specifically:

If you put a break point in, do you see any TeeChart classes in the call stack? Is there any clue that this is being caused by TeeChart? I don't see any reference to it in the error message.

Could you please send us the full callstack which the debugger gives you when it stops at the unhandled exception?

The third suggestion is to give us any logs that you might have in your application which could provide us with more information about the context of the exception.

[HCCKPM_2020]

Good Morning Christopher,

I tested 4.2020.5.12 and 4.2020.4.6: Both versions run without any problems. In my opinion that points to a problem in the newer dll.

How do you want to have the callstack? As dmp? I saved it as dmp. It's size is 1.7GB.

[Christopher]

How do you want to have the callstack? As dmp? I saved it as dmp. It's size is 1.7GB.

to reduce the size a little you could choose to save the dump as a 'minidump' instead of a 'minidump with heap', as explained here.

Can you use your OneDrive account, the one you used here, to transfer the minidump to us?

[HCCKPM_2020]

Hi Christopher,

I uploaded the file to https://hcckpm-my.sharepoint.com/:u:/g/ ... g?e=S01w5R

[Christopher]

I uploaded the file to https://hcckpm-my.sharepoint.com/:u:/g/ ... g?e=S01w5R

Thank you.

Having opened the file in Visual Studio 2019, the first thing I note is that TeeChart is not listed as one of the referenced modules:

devenv_2020-10-20_11-23-25.png (55.61 KiB) Viewed 22925 times

Then I run 'Debug with Managed Only':

devenv_2020-10-20_11-22-46.png (53.09 KiB) Viewed 22925 times

And finally, after waiting nearly 30 minutes for all the debug symbols to download, I see the results of running 'Debug with Mixed':

devenv_2020-10-20_11-22-10.png (59.24 KiB) Viewed 22925 times

Do you have any idea how I can use this dump to determine a problem related to TeeChart.WPF.dll, in the absence of any managed code to debug?

[HCCKPM_2020]

Hi,
I never used any Dumpfile for debugging.
All I can say is that using the latest version of your DLL the App crahses and using an older DLL it doesn't.
It's hard to understand why that information isn't enough? And if you have any suggestion on what can be the reason, logging could be a good way to detect the fault.

[Christopher]

All I can say is that using the latest version of your DLL the App crahses and using an older DLL it doesn't.
It's hard to understand why that information isn't enough?

We cannot reproduce your problem here, because you have been unable to provide us with an SSCCE. We cannot reproduce the assembly you say that works at your end using exactly the same code as that with which the working assembly was built, either with or without obfuscation. The dumpfile you sent us makes no reference to a TeeChart module whatseover, and has no managed code to debug. It does seem strange to suggest that given these circumstances you cannot understand why we can't resolve your issue.

There is one more possibility left, however, that I will have to discuss with colleagues tomorrow before I can confirm it to you.

[Christopher]

There is one more possibility left, however, that I will have to discuss with colleagues tomorrow before I can confirm it to you.

Just to let you know that I have sent you an email to the address associated with the account on this site.