RenameTabItemCount script memory leak?

Help & Support
1

In the afternoon i found, that my overall memory usage was very high, almost eating up my 16GB RAM space up to over 90%. Rainmeter showed me, that Opus used around 5.3GB of memory usage. I have found, that the memory usage is going up quickly, with almost every new click on a drive or a tab.

Then i noticed, after a Windows/Opus restart, that the RAM usage was going up from 1.8GB to 2.5GB after a few tabs clicked, and every new click immediately increased the amount of memory, which i believe is unusual (normally it would be under 2 Gigs).

I had Windows and Opus restarted then, but the memory went up with almost every drive or tab click, very quickly from 1.8GB to 2.5GB within a couple of minutes. Does anybody here experience something similar?

Edit, i wasn't sure if it was due to that script.

1 Like
2

Which script?

3

I meant RenameTabItemCount, which i had activated previous night. But i wasn't sure if it has to do with the RAM issue.

4

Have you tried deactivating it?

5

I would have thought the script was harmless but I have used it now for a few hours and Opus occupies 2.5 GB. That's certainly a bit odd :thinking:

6

I guess the script itself is harmless, but something along the way isn't. For example on Windows' side or another component.

7

Yes, i left it off after a test. Now Opus isn't even in the "top ten", which the module in Rainmeter displays.

8

I have observed this issue more closely and experimented with other scripts reacting to multiple events simultaneously. Somehow, these parallel-running events interfere with each other, causing incompletely prepared objects to be passed to scripts and tabs that are not fully loaded or have partially filled objects. For example, tab.all.count might return zero even when many files are present.

This issue is likely related to the empty tabs problem discussed here.

Would it make sense to create memory dumps when Opus becomes a bit "bloated"?

9

Thanks! We should have a fix for this in the next beta.

Well done for working out what script triggered it! Made reproducing it much easier.

2 Likes
10

Looking good. I monitored RAM usage all day today and saw a maximum of 360 MB :+1:

1 Like