Answer the question
In order to leave comments, you need to log in
How to solve this type of iOS Safari error: EXC_BAD_ACCESS?
I am writing a web application in a complex and new, for myself, area (canvas is used). On desktop browsers, the application works satisfactorily. I also checked the work on a budget smartphone Nokia Lumia 630 (WP 8.1 IE11) - the flight is excellent. But on iOS, the browser throws an error like: EXC_BAD_ACCESS. Surfing only hinted that there may be problems with memory (overloading or accessing carrier memory cells). After optimization, I reduced memory consumption to 20-40mb on different devices, but the error remains unchanged. I hope someone can help understand the logs .
Answer the question
In order to leave comments, you need to log in
As far as I know, this is an appeal to a non-existent object. He has already been released when you send him a message. You need to keep track of who you "removed" ahead of time.
A similar error only in all Safari browsers. Self-written lib on js (without third-party libraries). Lots of math.
According to the log, the error is of the same nature
...
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000010
Exception Note: EXC_CORPSE_NOTIFY
...
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question