Home/ Questions/Q 538983
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-13T10:05:19+00:00

Apple Developer Reference Library has a class reference for WebPreferences I’ve searched SO, Dev

  • 0

Apple Developer Reference Library has a class reference for WebPreferences

I’ve searched SO, Dev Forums and Googled without any relevant results.

EXC_BAD_ACCESS signal is generated.

I can’t find a crash report.. its happening on the simulator. The debugger is called, and I don’t get a crash report.

EDIT

This is triggered when tapping a UITextField, leaving a UITextField or if a UITextField is set as first responder when loading a view (push on by a navigation controller).

It is not easy to reproduce. I can go for a hundred app-launch/debug cycles before it will happen again. And then it might happen 3 times in 5 launches.

I do have a thread list in the debugger that shows several references to WebPreferences.

alt text

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    You’re on the right track if you are using NSZombie. EXEC_BAD_ACCESS is caused by accessing released objects.

    It is normal for EXEC_BAD_ACCESS to “crash” in code paths that do not belong to you. Most likely your code created the over-released object.

    The key part of using NSZombie is running the malloc_history on the command line. You’ll get the call stack showing where the over-released object originated from. For example:
    alt text http://static.benford.name/malloc_history.png

    The screenshot shows my app crashing at [NSString stringByTrimmingCharactersInSet:] but that is certainly not who caused the crash.

    I technique I use is to look at the earliest code path that you own. Most of the time the mistake lies there.

    In this case, the object originated from the class [JTServiceHttpRequest requestFinished], in which I was not properly retaining a object.

    If all else fails, go through all your code paths listed and verify your use of proper memory management rules.

    My bet is that WebPreferences and UITextField behavior have nothing to do with the crash.

    • 0