NPAPI:ErrorReporting: Difference between revisions

← Older edit

NPAPI:ErrorReporting (view source)

Revision as of 18:59, 6 June 2011

416 bytes added , 6 June 2011

→‎Current Proposal

Josh

Confirmed users, Bureaucrats and Sysops emeriti

1,680

edits

@@ Line 29: / Line 29: @@
 * <code>flags</code>:
 ** Future use, no flags defined now.
-* <code>pMemBlock</code>: The starting address of the memory block which must contain textual UTF8/ASCII data. Non-textual data can be encoded as text before it is placed in a registered block.
+* <code>pMemBlock</code>: The starting address of the memory block.
 * <code>sizeOfMemBlock</code>: The size of the memory block in bytes
@@ Line 38: / Line 38: @@
 * <code>NPERR_NO_ERROR</code>: If successful
-If the API is called with same key that was registered earlier, then API call with succeed and call will override the old pointer and length values. The plugin can attempt to register multiple memory blocks.
+Registered buffers must contain textual UTF8/ASCII data which is <code>NULL</code> terminated. Non-textual data can be encoded as text before it is placed in a registered buffer.
+The browser will not read a registered buffer upon registration, thus there is no need to re-register after changing the contents of a registered buffer. The buffer will only be read from a crash handler. Registering memory address <code>NULL</code> (zero) will not be allowed, to avoid the issue in which a plugin might register the result of a <code>malloc</code> call without a <code>NULL</code> check.
+If the API is called with a key that has already been registered, the new registration will replace the old one. Plugins can attempt to register multiple buffers.
 Calling <code>NPN_GetValue</code> with new key <code>NPNVmaxCrashMemoryBlockSize</code> can be used to get the maximum amount of memory available for a plugin's block registration. This is not a per-block or per-instance limit, it is a per-plugin limit.