C1DbNavigator MemoryLeak

Posted by: ivan.stanojkovski on 13 October 2023, 8:05 am EST

  • Posted 13 October 2023, 8:05 am EST - Updated 13 October 2023, 8:10 am EST

    Hi

    We are facing a very “big” problem with C1DbNavigator and memory leak.

    The problem is that the GC does not clean up all GDI objects after closing the Form that contains the C1DbNavigator control.

    Here you have an attached example with two forms.

    C1DbNavigator MemoryLeak.zip

    The first form (start-up) has a button that starts the second form (with Using statement and ShowDialog) in which there is a C1DbNavigator control.

    After closing the second form GDI objects remain in the Task Manager.

    Here is an example.

    1. Start of the application

    2. First time start of the form with C1DBNavigator

    3. First time to close the form with C1DBNavigator

    4. Second time to start the form with C1DBNavigator

    5. Second time to close the form with C1DBNavigator

    Do you have any suggestions on this topic?

    Thanks in advance.

  • Posted 15 October 2023, 5:17 pm EST

    Hi,

    Thanks for reaching out and providing the sample to replicate the issue.

    We are able to replicate this issue at our end. This seems like a bug. So, we have escalated this issue to the development team. Will get back to you once we have any update from them.[Internal Tracking Id - C1WIN-31213]

    Best Regards,

    Nitin

  • Posted 23 February 2024, 12:14 am EST

    Hi,

    The issue is fixed with the latest build.

    Please refer the sample with the latest C1 2023v3 Hotfix version: WinFormsApp1.zip

    Regards,

    Nitin

  • Posted 25 February 2024, 5:27 am EST

    Hi,

    I see that this issue is solved in v3 version only for .NET version

    NuGet → C1.Win.Input.DbNavigator → version 8.0.20233.636

    But not in the:

    NuGet → C1.Win.C1Input.C1DbNavigator → version 4.8.20233.636

    Is it possible in the future to solve this issue also in the Framework versions.

    Best regards.

  • Posted 25 February 2024, 7:40 pm EST

    Hi,

    Apologize for the inconvenience.

    We are discussing this with the development team for the fix under the .Net 4.8 Framework version. Will let you know once we get any updates ASAP.

    regards,

    Nitin

Need extra support?

Upgrade your support plan and get personal unlimited phone support with our customer engagement team

Learn More

Forum Channels