08-16-2012 09:03 AM
I am developing one application which is showing images one by one.
To handle that I had taken the touchevent and according to point next and previous image is shown.
But in that only while user encounters the tap event I am showing the information regarding the image in the custom dialog.
While handling this thing sometime app continuously crashes.
Any one is encountering this kind on propblem in latest bb10 realese.
Thanks in advance.
Solved! Go to Solution.
08-16-2012 10:51 AM - edited 08-16-2012 10:52 AM
How much progress have you made in your own debugging?
- what's the stack trace where you crash?
- have you checked that the object you are using is valid?
- have you got any trace?
- have you verified that all your own objects are properly created?
- have you double-checked that objects you are trying to use haven't been deleted?
- does this happen right away or only the 2nd time you process an image, or the 1000th? Is there a pattern that might lead you to where the crash is?
Based on what you've said so far, the problem is highly likely in your code. If you are stuck or suspect a cascades bug, can you provide a bit more context, code, debug trace, and the like?
08-17-2012 12:35 AM
08-17-2012 09:01 AM
This kind of bug can be very difficult to track down
Often it is a memory overwrite, an uninitialized variable, object used after being deleted but the memory is still somewhat valid, a specific sequence that must be hit, or coordination between threads. There are tools to help track down memory issues. You might want to spend some time writing defensive code and just sanitizing your code: in every constructor of yours, make sure you initialize all integers, doubles and pointers (even if you set the values later in the body or an Init function). Every place that can return 0, e.g. findChild or dynamic_cast, check if the returned pointer is 0 and log if it is.
To get some idea of where it might lie, sometimes I just add conditional-compile logging at the top of routines. Then I can trace what went on just before the crash. In your case, since gesture support is involved, I'd focus on exactly what is going on in that handling, and have your code report the moment something unusual happens.