It's a very common mistake that people make if they don't understand why memory usage is important. People can and do make things like several colossal image tiles, or a sprite with 100 animation frames which are 1024x1024 (which uses nearly half a gigabyte of memory alone), etc. Based on years of seeing things like this, it would be my first suspicion; next up I'd suspect a GPU driver bug since those are pretty common too.
For the record, neither your events nor Construct can typically crash the entire app. That means either out of memory (my first guess) or native code crashed (probably the driver, my second guess). Neither is actually Construct's fault. But really we can only guess based on the limited information provided - dop2000 is right that the only way to properly diagnose this would be to check LogCat, but often issues like this only happen with other people's devices, so you don't immediately have a way to test that, so you have to resort to guessing like this.