Version 2019 memory problem

  1. ‹ Older
  2. 3 weeks ago

    Rick A

    Oct 23 Pre-Release Testers (Brazil. GMT-3:00)

    @Payam A I sent a bug report and added my project to the report

    What's the feedback report number?

  3. Payam A

    Oct 23 Pre-Release Testers, Xojo Pro

    57995,
    but it's a private conversation.

  4. Rick A

    Oct 23 Pre-Release Testers (Brazil. GMT-3:00)

    @Payam A but it's a private conversation.

    Why? Is it because there is private code within it? If so, couldn't you replicate the problem with a simple public one? The course of this conversation is of public interest. :(

  5. Payam A

    Oct 23 Pre-Release Testers, Xojo Pro

    It's because I enclosed my whole project.

  6. Jürg O

    Oct 23 Pre-Release Testers, Xojo Pro
    Edited 3 weeks ago

    @Payam A It's because I enclosed my whole project.

    What you can do:

    1. Create a new public Feedback. Explain what it is about.
    2. Use "Add Info" to attach your private project. For this "added info" you set the visibility to "only me & xojo".
    3. Do the same for any further (public / private) information you'd like to add -> set visibility accordingly

    That way, the Feedback can be seen and found by everyone. But only Xojo gets access to the private Info with added private project.

  7. 2 weeks ago

    Yoann B

    Oct 29 Pre-Release Testers
    Edited 2 weeks ago

    When I removed the container controls from the window, memory usage decreased from 1.2GB to 430MB. Did you try to remove the container controls to see whether memory usage decreases or not ?

    @Payam A I have many controls in the window, and I also have containers.

    I don't know about Instruments.

    I don't think that I have memory leaks, because the memory does not increase gradually. It gets very high, when I make the window larger, and then the memory remains at the same level, until I do something else.

    What I want to say is that previous to Xojo 2019 this problem did not exist at all. So the problem must be with the programming language rather than with my app.

  8. Rick A

    Oct 29 Pre-Release Testers (Brazil. GMT-3:00)
    Edited 2 weeks ago

    Container Controls seems problematic, and memory auto release in other cases seems problematic too.

    Feedback Case #41624
    Feedback Case #47818
    Feedback Case #45697
    Feedback Case #40082

    Even Xojo seems affected:

    Feedback Case #27264

  9. Martin T

    Oct 29 Pre-Release Testers Germany

    I have been observing this behavior for quite some time and am dependent on the use of ContainerControls. Hopefully Xojo will slowly take on the feedback cases mentioned by Rick.

  10. last week

    Payam A

    Nov 2 Pre-Release Testers, Xojo Pro

    @Yoann B When I removed the container controls from the window, memory usage decreased from 1.2GB to 430MB.

    I also removed one container control from my window, but that didn't change anything. Maybe all container controls must be removed, but that is something I can't do, because I have too much code referring to those controls.

  11. Norman P

    Nov 2 Pre-Release Testers, Xojo Pro great-white-software.com/blog

    The IDE uses a lot of container controls
    Does it continue to gobble up memory for you ?

  12. Payam A

    Nov 2 Pre-Release Testers, Xojo Pro

    I don't see any difference between IDEs of Xojo 2018.3 and 2019. The problem is related only to my app.

  13. Payam A

    Nov 2 Pre-Release Testers, Xojo Pro

    There is a clear difference, however, between Xojo 2017 and 2019. The former uses around 270 MB at launch, the latter uses around 700 MB.

  14. Payam A

    Nov 2 Pre-Release Testers, Xojo Pro

    @Norman P When I open my project with Xojo 2017 and select my MainWindow tab, memory usage is around 520 MB. If I do the same thing with Xojo 2019.2 or 2018.3, memory usage is around 1.40 GB.

  15. Norman P

    Nov 2 Pre-Release Testers, Xojo Pro great-white-software.com/blog
    Edited last week

    have you enabled Support for HiDPI or Dark mode ?
    that will use up more memory

    I dont see where anyone has asked if this is on macOS or Windows or Linux or ??????

  16. Payam A

    Nov 2 Pre-Release Testers, Xojo Pro

    @Norman P I am testing on macOS.
    If HiDPI and Dark mode are not enabled, memory usage for my app at startup is 117 MB with Xojo 2017.3 and 208 MB with Xojo 2019.2. This seems normal.
    If HiDPI is enabled, memory usage is 215 MB with Xojo 2017.3. However, with Xojo 2019.2, memory usage is around 560 MB at startup. And then if I work with my app, memory can go up to 1.50 GB. So the problem seems to be related to the HiDPI property for both the IDE and apps.

  17. Payam A

    Nov 2 Pre-Release Testers, Xojo Pro

    I have to take back that the problem with the IDE is related to HiDPI, because Xojo 2017.3 seems also to work with HiDPI, but the IDE does not use so much memory. I also want to add that my Xojo 2017.3 has more plugins than Xojo 2019.2 and is around 270 MB of memory. But Xojo 2019.2 with the same plugins is almost at 1 GB at startup (!)

  18. Payam A

    Nov 2 Pre-Release Testers, Xojo Pro

    I asked myself whether the problem is related to third party plugins. However, if I open my project with Xojo 2017.3 with all plugins included, I'm around 520 MB. Now with Xojo 2019.2, even without any third party plugins, I'm at 1 GB when I open my project. At startup, however, Xojo 2019.2 is around 270 MB without plugins. It is only when the IDE is opened with my project that the memory increases dramatically----in the case where there are no third party plugins.

  19. Yoann B

    Nov 3 Pre-Release Testers
    Edited last week

    @Norman P have you enabled Support for HiDPI or Dark mode ?
    that will use up more memory

    I dont see where anyone has asked if this is on macOS or Windows or Linux or ??????

    As I said earlier in the thread, It only happens for me with macOS 64 built apps. Windows apps is fine. I did not test on Linux.

    No Dark mode, HiDPI enabled on 2017R3 and 2019R11.

    I tested with all Xojo versions from 2017R3 to 2019R2. The huge memory usage appears from 2018R4.

  20. Yoann B

    Nov 3 Pre-Release Testers

    @Payam A I asked myself whether the problem is related to third party plugins. However, if I open my project with Xojo 2017.3 with all plugins included, I'm around 520 MB. Now with Xojo 2019.2, even without any third party plugins, I'm at 1 GB when I open my project. At startup, however, Xojo 2019.2 is around 270 MB without plugins. It is only when the IDE is opened with my project that the memory increases dramatically----in the case where there are no third party plugins.

    I removed plugins one by one up to a certain point (when I had to do more than 3 000 changes in my code) and it changed nothing, I also tested every plugin I use with 2017 R3 and 2019 R11. No difference. The memory usage is identical. The only time when I see memory usage decrease is when I remove container controls from the main window.

    Does the Feedback app use container controls ? I am asking because I noticed that the latest version uses a lot of memory, like 2 GB for 15 bug reports open in the window.

  21. Norman P

    Nov 3 Pre-Release Testers, Xojo Pro great-white-software.com/blog

    feedback uses containers and htmlviewers as far as I know

or Sign Up to reply!