NPAPI:ErrorReporting: Difference between revisions

no edit summary
No edit summary
Line 61: Line 61:
* <code>NPERR_NO_ERROR</code>: memory successfully unregistered
* <code>NPERR_NO_ERROR</code>: memory successfully unregistered


== Open Issues ==
= Open Issues =


* We need to check with browser vendor crash reporting teams to make sure we can handle arbitrary blocks of memory. Right now, for example, I think Mozilla is only set up to handle string annotations and I'm not sure what additional challenges random memory will pose.
* We need to check with browser vendor crash reporting teams to make sure we can handle arbitrary blocks of memory. Right now, for example, I think Mozilla is only set up to handle string annotations and I'm not sure what additional challenges random memory will pose.
* Does <code>NPNVmaxCrashMemoryBlockSize</code> give the maximum size for a single registered block or all registered blocks?
* Does <code>NPNVmaxCrashMemoryBlockSize</code> give the maximum size for a single registered block or all registered blocks?
Confirmed users, Bureaucrats and Sysops emeriti
1,680

edits