Cascades Development

[lvandyk]

Whenever I perform any actions in the simulator my console gets spammed with messages like so:

### BAD_FRAME pid=34803824 at 5697794 ms -> t: 22 ms p1: 0 ms, r: 18 ms, p2: 0 ms, u: 3 ms
### BAD_FRAME pid=34803824 at 5697818 ms -> t: 23 ms p1: 0 ms, r: 19 ms, p2: 0 ms, u: 3 ms
### BAD_FRAME pid=34803824 at 5697851 ms -> t: 32 ms p1: 0 ms, r: 26 ms, p2: 0 ms, u: 4 ms
### BAD_FRAME pid=34803824 at 5697877 ms -> t: 25 ms p1: 0 ms, r: 19 ms, p2: 0 ms, u: 5 ms

Is there a way of disabling this?

More importantly, is it because I am doing something wrong? Everything works perfectly within my application.

This only started once I converted to BETA 2.

Thanks!

[blackqtcoder]

The same

[Neurocode]

I also get this, both with sample apps and my own.

[vingilot]

my situation is the same, I know just saying I have the same problem isn't helping anything but it will keep the thread active and hopefully someone knowledgable on this subject can resolve the issue for us.

[bb2cool]

I have the same problem. I am ignoring it :-)

[soaman]

I would like to know, too.

[iamjay]

Not just simulator. This happens on Dev Alpha device also.

[blackqtcoder]

Dou you view this errors in console, too ?

---------------------------------------------------------------------

ERROR:: QNXPpsSubscriptionServer: QNXPpsSubscriptionServer::createObject: (13) Failed to create dir /pps/services/automation/framework

ERROR:: QNXPpsSubscriptionServer: QNXPpsSubscriptionServer::subscribe: Failed to open /pps/services/automation/framework/control?delta,notify=492:00000001

Context: Failed to find target node with id  0

---------------------------------------------------------------------

Tested with StampCollector sample.

[vingilot]

I have had my share of fail to find target nodes, yes, any clarification on what that means as well would be quite useful.

[danielrr5 · Accepted solution]

Hi everyone, 

I asked internally and I've been told these are just junk messages that should not be output to the console. They will be removed in a future release of the OS.

So don't worry about it for now, they are not related to your app.

Regards, 

Daniel