RS-MET icon indicating copy to clipboard operation
RS-MET copied to clipboard

AsyncCallInvoker memory leak

Open elanhickler opened this issue 8 years ago • 15 comments

image

*** Leaked objects detected: 1 instance(s) of class AsyncCallInvoker
JUCE Assertion failure in memory/juce_LeakedObjectDetector.h:88

tested on Mushroom Generator

elanhickler avatar Jan 06 '18 22:01 elanhickler

can't build it. i'm getting:

class "rosic::BreakpointModulator" has no member "setStrategy" class "rosic::BreakpointModulator" has no member "rebuildCursorStrategyBuffer"

btw.: are you going to fix your compiler warnings? most of them are implicit type conversion warnings which are trivial to fix by adding explicit conversion. i.e. instead of int myInt = myDouble; write int myInt = (int)myDouble; or int myInt = int(myDouble); for example. you will sometimes have to take care of using parentheses correctly to apply the conversion to the final result in expressions. for example: int myInt = (int)myDouble1 + myDouble2; will still trigger it. you will need: int myInt = int(myDouble1 + myDouble2);

RobinSchmidt avatar Jan 07 '18 13:01 RobinSchmidt

try testing with prettyscope. working on warnings now.

elanhickler avatar Jan 07 '18 17:01 elanhickler

ok - but what should i do? i haven't seen this yet

RobinSchmidt avatar Jan 07 '18 17:01 RobinSchmidt

huh, I think a few issues were solved somehow.

elanhickler avatar Jan 07 '18 18:01 elanhickler

haha! what? how? which ones?

RobinSchmidt avatar Jan 07 '18 18:01 RobinSchmidt

maybe just this one.

elanhickler avatar Jan 07 '18 18:01 elanhickler

ok - good news anyway

RobinSchmidt avatar Jan 07 '18 18:01 RobinSchmidt

...after fixing the warnings?

RobinSchmidt avatar Jan 07 '18 18:01 RobinSchmidt

nevermind.......... no issues solved.

elanhickler avatar Jan 07 '18 18:01 elanhickler

these issues seem to be intermittent

elanhickler avatar Jan 07 '18 18:01 elanhickler

this smells like threading issues. these are the hardest nuts to debug. but what is a situation where this may occur?

RobinSchmidt avatar Jan 07 '18 18:01 RobinSchmidt

don't know yet, focus on the issues that you can solve. im trying to figure this out.

sliders are messed up, i think because of the macro parameter stuff. moving a slider forward then back, you see the slider move forward for the first pixel of movement. ill make a new thread about this. But I think you're not finished with the macro stuff. Slider should not reflect current macro value.

elanhickler avatar Jan 07 '18 18:01 elanhickler

ill make a new thread about this. But I think you're not finished with the macro stuff. Slider should not reflect current macro value.

ok, do that. i actually think, it should, but let's discuss this there then

RobinSchmidt avatar Jan 07 '18 19:01 RobinSchmidt

close for now

elanhickler avatar Jan 08 '18 19:01 elanhickler

ok this is happening consistently now, build any of my plugins, VST version. But it's not a show stopper, so it's fine for now.

elanhickler avatar Jan 09 '18 15:01 elanhickler