Toolkit Pro - Exception on exit following 24.0 upgrade

Print Page | Close Window

Exception on exit following 24.0 upgrade

Printed From: Codejock Forums
Category: Codejock Products
Forum Name: Toolkit Pro
Forum Description: Topics Related to Codejock Toolkit Pro
URL: http://forum.codejock.com/forum_posts.asp?TID=24513
Printed Date: 03 December 2024 at 12:29pm
Software Version: Web Wiz Forums 12.04 - http://www.webwizforums.com

Topic: Exception on exit following 24.0 upgrade

Posted By: Heath
Subject: Exception on exit following 24.0 upgrade
Date Posted: 25 October 2024 at 7:38am

CJ: 24.0 (released)

VS@ 2022 (17.11.5)

I have a long standing VS 2020 MDI C++ app using many CJ controls and views.

As recommended I changed the base app class from CWinApp to CXTPWinApp.

Application runs fine but during the CXTPWinApp:ExitInstance an assert is thrown in CMap.

MyApp.exe!CMap<unsigned __int64,unsigned __int64,void *,void * &>::RemoveKey(unsigned __int64 key) Line 1615 C++

MyApp.exe!XTPTlsFree(unsigned __int64 dwSlot) Line 3124 C++

MyApp.exe!CXTPThreadLocal<CXTPMarkupString>::~CXTPThreadLocal<CXTPMarkupString>() Line 1729 C++

MyApp.exe!`dynamic at exit destructor for 'g_xtpMarkupStringRelativeToBoundingBox''() C++

Spent most of the week on this and I'm under pressure to rollback to CJ 22.x.

Any help would be greatly appreciated.

Regards,

Heath

Replies:

Posted By: cpede
Date Posted: 31 October 2024 at 8:21am

I have something similar, where I have a explicitly loaded DLL that cannot be freed because "something" in XTToolkit is holding it back, a reference count, hook or something like that.

I had similar issues like you, and my only suggestion is to ensure that you do not call XTPShutdown() yourself in your code, since this is now handled by CXTPWinApp.

I hope that CodeJock will make a lot more debug information around the cleaning up procedures in an update.

-------------
Product: Xtreme ToolkitPro (24.0.0)
Platform: Windows 10 (x64)
Language: Visual Studio 2017 (C++)

Posted By: Heath
Date Posted: 01 November 2024 at 8:53am

Thanks for your suggestion, but I'm not running XTPShutdown. I do agree, some more debug logging around the global functions would be welcomed.

I'm in touch with support and have sent a test project that exhibits the issue and a call stack.

Thanks,

Heath