# High memory usage because of TRAKTOR4 tag field
**URL:** https://community.mp3tag.de/t/high-memory-usage-because-of-traktor4-tag-field/67487
**Category:** General Discussion
**Created:** [February 12, 2025, 3:49pm UTC](https://community.mp3tag.de/t/high-memory-usage-because-of-traktor4-tag-field/67487 "2025-02-12T15:49:46Z")
**Posts on this page:** 6
**Page:** 1
### Author:  [@viviancels](https://community.mp3tag.de/u/viviancels)
#### Post date: [February 12, 2025, 3:49pm UTC](https://community.mp3tag.de/t/high-memory-usage-because-of-traktor4-tag-field/67487/1 "2025-02-12T15:49:46Z")
Hello, I try to edit tag of 3000 files, I have 32GB memory
I push "abort" operation, but memory still leaks.
---
### Author:  [@Florian](https://community.mp3tag.de/u/Florian)
#### Post date: [February 12, 2025, 3:57pm UTC](https://community.mp3tag.de/t/high-memory-usage-because-of-traktor4-tag-field/67487/2 "2025-02-12T15:57:26Z")
It's very likely that the memory is related to undo data that is preserved in memory to allow for undoing the edit tag operations.
You can reset this by loading another directory.
---
### Author:  [@viviancels](https://community.mp3tag.de/u/viviancels)
#### Post date: [February 13, 2025, 10:09am UTC](https://community.mp3tag.de/t/high-memory-usage-because-of-traktor4-tag-field/67487/3 "2025-02-13T10:09:52Z")
OMG I understood, why I have problem. I applied difference "regexp" and another "replace" actions to FLAC files with Traktor 3 tag in. Traktor 3 writes trash tag like this : [Context – share whatever you see with others in seconds](https://ctxt.io/2/AAB4ui0WEQ)
For this reason, I do not allow the Traktor 3 to write a tag to files, besides, the Traktor 3 removes multitegs or interferes with other tags, which is illogical and impermissible. Therefore, when I define BPM in the Traktor 3, I manually transfer chunks of the list to mp3tag. This trash Traktor 3 tag was written in FLACs years ago
So regular expressions kills memory of PC when try apply regexp formulas to this large chunk of 407 000 character garbage contained in the Traktor 3 tag ))))))
To solve problem must create first action: format value: field: TRAKTOR4 / format string: %null%
---
### Author:  [@LyricsLover](https://community.mp3tag.de/u/LyricsLover)
#### Post date: [February 13, 2025, 10:49am UTC](https://community.mp3tag.de/t/high-memory-usage-because-of-traktor4-tag-field/67487/4 "2025-02-13T10:49:17Z")
> [@viviancels](#):
>
> To solve problem must create first action: format value: field: TRAKTOR4 / format string: %null%
`%null%`? Are you sure?
Usually you would use the Action "[Remove fields](https://docs.mp3tag.de/actions/remove-fields/)" for such a task.
Do you remember this topic?
> [@Remove TRAKTOR-specific fields from FLAC](https://community.mp3tag.de/t/remove-traktor-specific-fields-from-flac/58446/3):
>
> Do you see it via extended tags at Alt+T. If so, remove it from there.
Just for the record:
_(because the above link to [ctxt.io](http://ctxt.io) with the example tag content expires in 30 days)_
---
### Author:  [@viviancels](https://community.mp3tag.de/u/viviancels)
#### Post date: [February 13, 2025, 12:59pm UTC](https://community.mp3tag.de/t/high-memory-usage-because-of-traktor4-tag-field/67487/5 "2025-02-13T12:59:32Z")
> [@LyricsLover](#):
>
> Do you remember this topic?
Yes, these tracks from that 2022 case. I always thought, that %null% & %dummy% delete values and remove field, after I %null% the tag I dont see this tag in Alt+T
---
### Author:  [@Florian](https://community.mp3tag.de/u/Florian)
#### Post date: [February 13, 2025, 1:05pm UTC](https://community.mp3tag.de/t/high-memory-usage-because-of-traktor4-tag-field/67487/6 "2025-02-13T13:05:33Z")
> [@viviancels](#):
>
> I always thought, that %null% & %dummy% delete values and remove field, after I %null% the tag I dont see this tag in Alt+T
Yes, if the field contents are removed the tag field itself is removed too.
In this specific case, your files don't have a field named `NULL` and you assign the empty value to the `TRAKTOR4` field, which eventually results in its removal.
* * *
I've renamed the topic title accordingly, to make it less misleading: it's high memory usage, not a memory leak.