Isadora crash after about 10 hours

Lauri

@DusX and @mark Many thanks for your replies!

@mark Yes, my project involves "Capture Stage to Movie" actor. My compression setting was Animation, 50fps, no keyframes, thousands of colors. At least with this codec the crashing is persistent. But I will try another codec too, before opening the ticket.

@DusX and @mark Yes, I will open a ticket soon.

Thanks again,

Lauri

Lauri

@DusX @mark I sent a support ticket just a moment ago, and attached the (simplified) project file and several crash reports. It seems like a memory leak issue, RAM seems to fill up constantly until crash.

mark

@lauri said:

I sent a support ticket just a moment ago, and attached the (simplified) project file and several crash reports. It seems like a memory leak issue, RAM seems to fill up constantly until crash.

OK. I will be able to examine this a bit later tonight. @lauri, I'm on it.

mark

@Lauri said:

I sent a support ticket just a moment ago

I just sent you a fix. Please try it and report back. I have high confidence I solved your issue.

Best Wishes,
Mark

DusX

@mark @Lauri

I have been running the test file using the fix for an hour now and it appears to be corrected.

Lauri

@mark Thousand thanks for the fix! @DusX Thanks for testing it.

I'm now in Vienna, returning back next weekend, will test it as soon as getting back.

Thanks!

Lauri

Lauri

@mark @DusX Thank you again for looking at the memory leak issue. Since the time you sent the links to beta version (below), I’ve been doing tests with it and found that there’s still some sort of a memory leak.

Here are my results in a MacPro (late 2013) that has 64GB RAM installed:
- 6GB RAM (Memory Used) when project started
- 20GB RAM (Memory Used) after running project for 18hours
- 21GB RAM (Memory Used) after running project for 19hours
- 24GB RAM (Memory Used) after running project for 28hours
- 38GB RAM (Memory Used) after running project for 42hours

I’ve noticed that the more the RAM gets filled, the slower the project runs (cycles and fps drop), at least with a bit more complicated project file than I sent you before. However, the RAM results you see above come also with running the project I sent you. I haven't got Isadora crashing on this kind of project, or maybe I’ve not run it long enough, but while the RAM gets filled it at least slows Isadora down.

Would you be willing to look again at this issue?

I have another request (that I already posted to the forum) concerning the Capture Stage to Disk actor functions. See the explanation here:
https://community.troikatronix.com/topic/5126/request-for-capture-stage-to-disk-actor-behavior-change
Do you think this change could be done?

Please let me know, if you have any questions.

Many thanks in advance!

Lauri

Lauri

@mark Thousand thanks for the beta3! I've now tested it for a bit longer, and found that there's still a small leak. I ran a patch (with Capture Stage to Disk actor) for eleven days with my MacPro, and the RAM was filling up about 30MB/hour, which really is not much, but for a longer term... I repeated running the patch for another 4 days with similar results.

I also ran the patch on a MacBookPro, which gave same outcome, but I did not have a chance to run it more than overnight.

Also, on MacPro (late 2013, trashcan)and Isadora v.2.6.2b3 the cycles go down strangely after some time. With my patch, it runs around 460-515 for about 7mins, then starts to decrease slowly down to around 100, and then jumps fast back to around 460-515… Did not notice this phenomenon on my MacBookPro.

So, the leak is a minor one. However, if you are not able to fix this memory leak for Isadora v2.x, I hope you could ensure it's gone with the coming version Isadora 3.x?

Thanks in advance,

Lauri

Lauri

I’m sorry to return to this issue after couple of years, but I just found out that Isadora 3 (at least version 3.0.7) has a memory leak. I was running a patch and found out that the consumption of RAM grew about 1,3GB per 12h (that makes 2,6GB/day) on my MacBookPro. (No crash or out-of-RAM as my MBP has 32GB.)

I’m mostly working with long running exhibition installations when using Isadora, and memory leaks are lethal for those.

Thanks again in advance!

mark

@lauri said:

I’m sorry to return to this issue after couple of years, but I just found out that Isadora 3 (at least version 3.0.7) has a memory leak. I was running a patch and found out that the consumption of RAM grew about 1,3GB per 12h (that makes 2,6GB/day) on my MacBookPro. (No crash or out-of-RAM as my MBP has 32GB.)

We know about this. Go to the Isadora Preferences > General > Frame Rate/Tasks. Set the Display Refresh Lock to 'off' and restart Isadora.

I'm 99.9% sure this will solve your problem. Please report back either way.

Best Wishes + Stay Safe,
Mark

Lauri

@mark

Thousand thanks for your reply!

Unfortunately your advice didn’t change the situation as the “Display Refresh Lock” was already set to “off”.

I made another test with a similar kind of patch, but this time with Capture Stage to Movie involved, and that resulted even higher growth of RAM usage (around 6GB/day).

I started another test today with a similar patch with my MacPro (trashcan), and will report the results of that in a couple of days.

However, there still seems to be a memory leak in Isadora v3.0.7 at least on my MacBookPro. Should I make a support ticket?

mark

@lauri said:

However, there still seems to be a memory leak in Isadora v3.0.7 at least on my MacBookPro. Should I make a support ticket?

Yes. Please do.

Best Wishes,
Mark

Lauri

Dear @mark

It’s now almost ten months that I made the support ticket to solve the bug that makes my patches freeze Isadora.

I told you in end of April that I was not in a hurry. However, I would really need a solution now. I need to finish the project soon, and I cannot do that if Isadora keeps freezing.

I have began to doubt that it's about a memory leak, but hopefully you could find the culprit. So, I made some further tests and attached them (test results and the patches) to the old support ticket. I sincerely hope you could look into this problem now.

Thousand thanks in advance!

Best, Lauri