If it does not give any error, then there must be a reason for it normally, because the most common thing that would happen is a MAV or media not found crash.
I assume you are using strict everywhere?
Theoretically the only difference between release and debug are the debug stuff thats used to check loops and array bounds
Btw: the fact that it does not break with array in debug does not mean that they aren't the problem. Dont forget that loops are several times slower in debug than in release, so the app must run much longer to reach the same point ie the same type of errors as the release version. To test such stuff, declare methods / function you know they work correctly, as nodebug (ex: method test() nodebug). That way, loops in them run on release speed even in debug and you might find your problem after all.
I assume you are using strict everywhere?
Theoretically the only difference between release and debug are the debug stuff thats used to check loops and array bounds
Btw: the fact that it does not break with array in debug does not mean that they aren't the problem. Dont forget that loops are several times slower in debug than in release, so the app must run much longer to reach the same point ie the same type of errors as the release version. To test such stuff, declare methods / function you know they work correctly, as nodebug (ex: method test() nodebug). That way, loops in them run on release speed even in debug and you might find your problem after all.