Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

In this Discussion

Codea quits, how to investigate?

in Questions Posts: 166

I have a project which sometimes quits codea when I run it. I suspect it’s a memory thing, but I’m not sure how to go about investigating this.

The project makes use of a number of classes.

Comments

  • dave1707dave1707 Mod
    Posts: 6,993

    How long does it run before it quits. Do you use a lot of tables, are you using Craft, are you doing a lot of graphics. Without seeing any code or knowing what the code is doing, it’s hard to say what to look for

  • edited March 26 Posts: 923

    @Kirl - what system (iPad) and iOS version are you? What memory size?

    There are a few tricks that you can use to check for exceeding memory levels, we’ll check those out and post. As @dave1707 has mentioned, showing us some of the code will also help. Is your code extensive, if so can you rem out sections to try to identify the routines which are causing the problem. The time to Codea dropout may give us a hint - but we need to see some code!

  • edited March 27 Posts: 923

    @Kirl - to check for continual memory loss use the following two lines at the end of your draw() function:


    output.clear() print(collectgarbage("count"))

    Search on the forum for an FPS routine which will check for processor usage, best running at 60 FPS (frames per second).

    Gives you a good start to monitoring problems.

Sign In or Register to comment.