1 /* Copyright (c) 2012 The Chromium Authors. All rights reserved.
2 * Use of this source code is governed by a BSD-style license that can be
3 * found in the LICENSE file.
7 * This file defines an enumeration of all PPAPI error codes.
11 * This enumeration contains enumerators of all PPAPI error codes.
13 * Errors are negative valued. Callers should treat all negative values as a
14 * failure, even if it's not in the list, since the possible errors are likely
15 * to expand and change over time.
17 [unnamed
] enum PP_Error
{
19 * This value is returned by a function on successful synchronous completion
20 * or is passed as a result to a PP_CompletionCallback_Func on successful
21 * asynchronous completion.
25 * This value is returned by a function that accepts a PP_CompletionCallback
26 * and cannot complete synchronously. This code indicates that the given
27 * callback will be asynchronously notified of the final result once it is
30 PP_OK_COMPLETIONPENDING
= -1,
32 /**This value indicates failure for unspecified reasons. */
36 * This value indicates failure due to an asynchronous operation being
37 * interrupted. The most common cause of this error code is destroying a
38 * resource that still has a callback pending. All callbacks are guaranteed
39 * to execute, so any callbacks pending on a destroyed resource will be
40 * issued with PP_ERROR_ABORTED.
42 * If you get an aborted notification that you aren't expecting, check to
43 * make sure that the resource you're using is still in scope. A common
44 * mistake is to create a resource on the stack, which will destroy the
45 * resource as soon as the function returns.
47 PP_ERROR_ABORTED
= -3,
49 /** This value indicates failure due to an invalid argument. */
50 PP_ERROR_BADARGUMENT
= -4,
52 /** This value indicates failure due to an invalid PP_Resource. */
53 PP_ERROR_BADRESOURCE
= -5,
55 /** This value indicates failure due to an unavailable PPAPI interface. */
56 PP_ERROR_NOINTERFACE
= -6,
58 /** This value indicates failure due to insufficient privileges. */
59 PP_ERROR_NOACCESS
= -7,
61 /** This value indicates failure due to insufficient memory. */
62 PP_ERROR_NOMEMORY
= -8,
64 /** This value indicates failure due to insufficient storage space. */
65 PP_ERROR_NOSPACE
= -9,
67 /** This value indicates failure due to insufficient storage quota. */
68 PP_ERROR_NOQUOTA
= -10,
71 * This value indicates failure due to an action already being in
74 PP_ERROR_INPROGRESS
= -11,
77 * The requested command is not supported by the browser.
79 PP_ERROR_NOTSUPPORTED
= -12,
82 * Returned if you try to use a null completion callback to "block until
83 * complete" on the main thread. Blocking the main thread is not permitted
84 * to keep the browser responsive (otherwise, you may not be able to handle
85 * input events, and there are reentrancy and deadlock issues).
87 PP_ERROR_BLOCKS_MAIN_THREAD
= -13,
89 /** This value indicates failure due to a file that does not exist. */
90 PP_ERROR_FILENOTFOUND
= -20,
91 /** This value indicates failure due to a file that already exists. */
92 PP_ERROR_FILEEXISTS
= -21,
93 /** This value indicates failure due to a file that is too big. */
94 PP_ERROR_FILETOOBIG
= -22,
96 * This value indicates failure due to a file having been modified
99 PP_ERROR_FILECHANGED
= -23,
100 /** This value indicates that the pathname does not reference a file. */
101 PP_ERROR_NOTAFILE
= -24,
102 /** This value indicates failure due to a time limit being exceeded. */
103 PP_ERROR_TIMEDOUT
= -30,
105 * This value indicates that the user cancelled rather than providing
108 PP_ERROR_USERCANCEL
= -40,
110 * This value indicates failure due to lack of a user gesture such as a
111 * mouse click or key input event. Examples of actions requiring a user
112 * gesture are showing the file chooser dialog and going into fullscreen
115 PP_ERROR_NO_USER_GESTURE
= -41,
117 * This value indicates that the graphics context was lost due to a
118 * power management event.
120 PP_ERROR_CONTEXT_LOST
= -50,
122 * Indicates an attempt to make a PPAPI call on a thread without previously
123 * registering a message loop via PPB_MessageLoop.AttachToCurrentThread.
124 * Without this registration step, no PPAPI calls are supported.
126 PP_ERROR_NO_MESSAGE_LOOP
= -51,
128 * Indicates that the requested operation is not permitted on the current
131 PP_ERROR_WRONG_THREAD
= -52,
133 * This value indicates that the connection was closed. For TCP sockets, it
134 * corresponds to a TCP FIN.
136 PP_ERROR_CONNECTION_CLOSED
= -100,
138 * This value indicates that the connection was reset. For TCP sockets, it
139 * corresponds to a TCP RST.
141 PP_ERROR_CONNECTION_RESET
= -101,
143 * This value indicates that the connection attempt was refused.
145 PP_ERROR_CONNECTION_REFUSED
= -102,
147 * This value indicates that the connection was aborted. For TCP sockets, it
148 * means the connection timed out as a result of not receiving an ACK for data
149 * sent. This can include a FIN packet that did not get ACK'd.
151 PP_ERROR_CONNECTION_ABORTED
= -103,
153 * This value indicates that the connection attempt failed.
155 PP_ERROR_CONNECTION_FAILED
= -104,
157 * This value indicates that the connection attempt timed out.
159 PP_ERROR_CONNECTION_TIMEDOUT
= -105,
161 * This value indicates that the IP address or port number is invalid.
163 PP_ERROR_ADDRESS_INVALID
= -106,
165 * This value indicates that the IP address is unreachable. This usually means
166 * that there is no route to the specified host or network.
168 PP_ERROR_ADDRESS_UNREACHABLE
= -107,
170 * This value is returned when attempting to bind an address that is already
173 PP_ERROR_ADDRESS_IN_USE
= -108,
175 * This value indicates that the message was too large for the transport.
177 PP_ERROR_MESSAGE_TOO_BIG
= -109,
179 * This value indicates that the host name could not be resolved.
181 PP_ERROR_NAME_NOT_RESOLVED
= -110