Exception on exit following 24.0 upgrade

Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic

   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

Author	Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic
Heath Members Profile Send Private Message Find Members Posts Add to Buddy List Groupie Joined: 05 April 2004 Status: Offline Points: 20	Post Options Post Reply Quote Heath Report Post Thanks(0) Quote Reply Topic: Exception on exit following 24.0 upgrade 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

cpede Members Profile Send Private Message Find Members Posts Add to Buddy List Senior Member Joined: 13 August 2004 Location: Denmark Status: Offline Points: 668	Post Options Post Reply Quote cpede Report Post Thanks(0) Quote Reply 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++)

Heath Members Profile Send Private Message Find Members Posts Add to Buddy List Groupie Joined: 05 April 2004 Status: Offline Points: 20	Post Options Post Reply Quote Heath Report Post Thanks(0) Quote Reply 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