Kinds of Error Reports

The Codetrails Error Analytics Server can handle a wide range of error reports, from the classic NullPointerException to UI freezes. For each kind of error report, the server performs specialized duplicate detection that understands the peculiarities of the given error’s stack trace(s).

Incidents and problems may be of one of these six kinds:

Normal Error

Normal errors are all exceptions that were reported by a client but that are not of kind defined below. Common examples of a normal error are a NullPointerException or IllegalArgumentException.

OutOfMemoryError (OOME)

An OutOfMemoryError is a special kind of exception. Unlike for normal errors, the stack frame (implicitly) throwing the exception is only sometimes indicative of the root cause of the problem.

StackOverflowError (SOE)

A StackOverflowError is a special kind of exception, whose unique characteristic is a repeating pattern of stack frames near the top of the stack trace.

UI Freeze

A UI freeze is caused by a long-running operation or even a deadlock on the UI thread. Eclipse’s built-in UI Responsiveness Monitoring logs these errors and the Eclipse IDE Client reports them.

Third-Party Error

Third-party errors are reports that were received by the Codetrails Error Analytics Server, which deemed neither the configured projects nor their dependencies at fault. Such errors will still be automatically assigned to a project based on the stack trace.

Third-Party UI Freeze

Third-Party UI Freezes are UI freezes that were received by the Codetrails Error Analytics Server, which deemed neither the configured projects nor their dependencies at fault. Such errors will still be automatically assigned to a project based on the stack trace.

results matching ""

    No results matching ""