Circular Dependency Error Occurrences`

it was from ages in my wf

app has member to view - mV

view has member to control - mC1, mC2

mC1 in its draw calls APP.getApp().mV.mC2.draw() for draw mC2 in AOD so venuSQ

so probably it's a problem, how to solve it?

maybe should be: APP.getApp().mV.weak().mC2.draw()

or rather

APP.getApp().mV.weak().get().mC2.draw()

?

any answer?

In order to be able to debug such a problem, sample code that reproduces the problem is necessary.

the problem is that that there is no circular ref in memory monitor, this happens only for venuSQ (all device run without problem and now silent with venuSQ too - no any changes)

and in strange place PSX1_Vie.:61 => line  class ViW extends UII.WatchFace so when app starts, no initialise yet I think

I've describe everything but one more thing:

- app has member to view - mV

- mV - view has members to control - mC1, mC2 (extends drawable) - public members

- in view onUpdate(dc) I call mC1.draw(dc)

- only when is AOD in mC1.draw(dc) calls APP.getApp().mV.mC2.draw(dc)

I think that is any problem with AOD/onEnterSleep/onExitSleep for all amoled and vivoactive4 family, I've report bug

_psx_ said:

the problem is that that there is no circular ref in memory monitor

While the term circular dependency error sounds similar, it is not the same as a circular reference error. The former occurs when a module initialization has an indirect dependency that requires itself be initialized; it causes a hard application crash. A circular reference error occurs when an object instance has an indirect reference to itself; it can cause memory leaks.

_psx_ said:

this happens only for venuSQ (all device run without problem and now silent with venuSQ too - no any changes)

It sounds like you were affected by a some sort of venusq issue that has since been fixed.

_psx_ said:

I've describe everything but one more thing:

Much like a picture is worth a thousand words, a code sample that can be used to directly reproduce the problem is worth dozens of hours of effort, especially when all of the required components of the failure are not known.