Some errors can seriously damage NetBeans execution and that can have impact on the ability to submit these errors via exceptions reporter.
Such errors are out of memory errors and deadlocks.
There's an idea to delay submission of these errors to the next start of NetBeans so that they can be reliably submitted.
So there are will be an API to submit the log record so they are sent at next start. Can you please specify and implement such API? If I understand correctly the log records will contain something special ... can you please post here an example how such records get created?
Also please note that OOME comes with heap dump (and deadlock with thread dump) that needs to be transferred. While thread dump might be written directly into the messages.log when the problem happens the heap dumps must be treated specially.
Implemented for OOME by changeset: 253319:601fcbcab54d
In changeset: 253324:0d284612b66e we use NbObjectInputStream so that DeadlockException is correctly resolved.
It should also cooperate well with the DeadlockException introduced by issue #206328. Therefore resolving as fixed.
Integrated into 'main-golden', will be available in build *201305142300* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress)
Log: #227668: OOME report is delayed after next start, since the IDE is likely in a bad state.