Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation


About EvgenKo423

  • Rank
    LAVA groupie

Profile Information

  • Gender

LabVIEW Information

  • Version
    LabVIEW 2018
  • Since

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Just wanna add to the topic that you can disable dump creation for DWarns by placing the following key into the INI file: NIERMaxDWarnDumps=0
  2. @dadreamer, nice find! Apparently these private properties should do exactly what you want: control SH behavior, but they allow to only control the size of large blocks (which shouldn't be the root of this problem) and don't seem to make any difference in my test anyway. Library replacement, on the other hand, eliminates this problem completely, even for blocks <256 bytes. Edit: Selective Deallocation is also available as an INI key along with a key "overanxiousMemoryDeallocation" (which doesn't help either).
  3. OK, thanks for your effort.
  4. Thanks for such a detailed explanation, Rob! I just played with string array a bit more and wanna share my findings with the others. According to SmartHeap specs, small should be considered blocks under 256 bytes, but LabVIEW starts to release memory as expected only for blocks which are 1048356 + 36 = 1048392 (1 MiB - 184) bytes in size and above. Is it still an expected behavior for LabVIEW? Anyway, even 256 bytes is probably quite big length for a typical string to get properly garbage-collected. TestStringArray.vi
  5. Unfortunately, it's still not fixed in LV 2018 SP1. Didn't check it specifically in 2020, but I guess it's the same. I wonder what happened to this CAR?
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.