Lines Matching refs:backend
6 // database operations don't delay the browser. This backend processing is
65 // Sends messages from the backend to us on the main thread. This must be a
68 // Release when the Backend has a reference to us).
83 history::InMemoryHistoryBackend* backend) OVERRIDE {
84 // Send the backend to the history service on the main thread.
86 &HistoryService::SetInMemoryBackend, backend));
149 // Shutdown the backend. This does nothing if Cleanup was already invoked.
154 // NOTE: We start the backend loading even though it completes asynchronously
156 // callers of this assume that if the backend isn't yet loaded it will be
158 // later. If we've purged the backend, we haven't necessarily restarted it
169 // Get rid of the in-memory backend.
172 // The backend's destructor must run on the history thread since it is not
174 // to the backend, or a crash could happen.
176 // We have a reference to the history backend. There is also an extra
177 // reference held by our delegate installed in the backend, which
179 // to HistoryBackend::Closing and *then* released our backend reference, there
180 // will be a race between us and the backend's Closing function to see who is
181 // the last holder of a reference. If the backend thread's Closing manages to
182 // run before we release our backend refptr, the last reference will be held
186 // a reference to the backend. Then we release our reference, then we schedule
201 // Unload the backend.
632 // notification (we don't have to wait for the backend, which allows us to
673 // Create the history backend.
768 // backend has allocated for us. The receiver of the notification will cast
779 scoped_refptr<HistoryBackend> backend(
783 history_backend_.swap(backend);
