Handling of inputs in a multi-process application

A non-transitory computer-readable medium for handling an event in an application, the computer-readable medium comprising instructions which, when executed by a computer, cause the computer to implement a method, the method comprising:

• executing, via a primary application at the computer,an embedder application, wherein the embedder application is associated with an embedder process, and wherein the embedder application outputs an embedder visual output;
• executing, via the primary application, a guest process, wherein the guest process executes in parallel with the embedder application, wherein the guest process is associated with a visual interface element, and wherein the visual interface element is within the embedder visual output;
• receiving, via the primary application, a user input within the visual interface element associated with the guest process, wherein the user input corresponds to an event to be handled:
• queuing, via the primary application:
• the event for handling by the guest process;
• dequeuing, via the primary application, the queued event in a case where the queued event is handled by the guest process within a threshold time period;
• and
• signaling, via the primary application, for handling the queued event by the embedder process in a case where the guest process crashes or in a case where the guest process is unresponsive during the threshold time period.

A system for handling an event in an application, the system comprising:

• one or more processors;
• and
• a memory comprising instructions which, when executed by the one or more processors, cause the one or more processors to implement a method, the method comprising:
• executing, via a primary application at a computing device, an embedder application, wherein the embedder application is associated with an embedder process, and wherein the embedder application outputs an embedder visual output;
• receiving, via the primary application, a user input within a visual interface element associated with a guest process, wherein the visual interface element is within the embedder visual output, and wherein the user input corresponds to an event to be handled;
• queuing, via the primary application, the event for handling by the guest process, wherein queuing the event for handling by the guest process comprises adding the event to a queue comprising a plurality of events for handling by the guest process;
• upon determining, via the primary application and at a first time, that the guest process crashes or that the guest process is unresponsive during a threshold time period:
• signaling for handling first unprocessed events in the queue by the embedder process;
• and
• upon determining, via the primary application and at a second time later than the first time, that the guest process is operational again:
• signaling for handling second unprocessed events in the queue by the guest process,
• wherein the first unprocessed events are unprocessed at the first time and wherein the second unprocessed events are unprocessed at the second time.