The frustum object is constructed in the main UI thread, from then on it's only touched in the rendering callback methods, which are all on the same thread.
On Jan 19, 10:46 am, Kostya Vasilyev <[email protected]> wrote: > I would try moving the initialization of "frustum" into the constructor, > and add log statements for array size(s) in the method. > > BTW, you said, no threading - but don't you have a separate rendering > thread? > > -- Kostya > > 19.01.2011 13:35, RyanMcNally пишет: > > > Does anyone have any suggestions on what diagnostics to add? The code > > is statically verifiable not to throw AIOOBEs, so I've got no idea > > what to check for at runtime. > > > Given that there is no threading, the arrays are defined exactly once, > > and the same indices are successfully written to 8 lines earlier and > > read from 2 lines earlier, I don't know what to check for. > > > On Jan 18, 10:07 pm, Frank Weiss<[email protected]> wrote: > >> I suggest catching the AIOBE and adding your own diagnostics, via a toast, > >> log, or analytics code. > > -- > Kostya Vasilyev -- WiFi Manager + pretty widget > --http://kmansoft.wordpress.com -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
