Skip to content
SPECIFICTION
Get listed

Crashpad vs NHN Cloud Log & Crash Search

Crashpad

chromium.googlesource.com

NHN Cloud Log & Crash Search

nhncloud.com

Side by side

FigureCrashpadNHN Cloud Log & Crash Search
Price fromFree—
Free planYes—
Free trial——
Open source——
Web—Yes
WindowsYesYes
macOSYes—
LinuxYes—
iOSYesYes
AndroidYesYes
API—Yes
Plans published11
Spec score · Game Crash Reporting Software8.7 (#10)7.2 (#22)
PurposeCrashpad is a library for capturing, storing, and transmitting postmortem crash reports from an application to a collection server.Collects and stores client and server application logs so users can view or search them.

Plans

Crashpad

  • CrashpadFree

Crashpad pricing →

NHN Cloud Log & Crash Search

  • Custom quotePriced on request

NHN Cloud Log & Crash Search pricing →

In their own words

Crashpad

Crashpad is an open-source crash-reporting system and client library for Android, iOS, Linux, macOS, and Windows. It embeds in an application, where a handler snapshots a registered process after a crash, saves a dump, and can send it to a collection server configured by the embedding client. Applications can also request process-state dumps on demand for diagnostics. Reports use the Windows minidump format with Crashpad extensions and generally contain loaded modules, thread registers and stack memory, selected operating-system state, and memory referenced by registers and stacks. Applications can add key/value annotations, application-specific metadata, and custom minidump streams. Uploads use HTTP or HTTPS through the Breakpad wire protocol, with a documented limit of one upload per hour and failed uploads aborted. The design requires applications to obtain and honor consent because process memory may contain sensitive data. Crashpad is a client-side component; a processor is planned without a completion timeline.

Visit chromium.googlesource.com

NHN Cloud Log & Crash Search

NHN Cloud Log & Crash Search collects and stores logs from client and server applications for viewing and searching. Logs can be sent to its collector over HTTP as JSON, including bulk delivery in JSON-array format. The Log Search API accepts Lucene queries and requires a project secret key in the request header. Searches cover logs from the previous 90 days, and each time range can span no more than 31 days. Results are returned in pages of up to 100 logs; the guide documents paging through up to 100,000 logs. HTTP ingestion requests are limited to 52 MB, while an individual JSON log can be 8 MB. Search usage consumes tokens based on duration, size, and query complexity, with replenishment over time. Source maps are supported. Platforms listed are Android, iOS, web, Windows, and API. Pricing is by custom estimate rather than a stated product price.

Visit nhncloud.com