Closed
Bug 492754
Opened 15 years ago
Closed 7 years ago
Exception when trying to bookmark a page while there is no space left on device [nsINavBookmarksService.insertBookmark]
Categories
(Toolkit :: Places, defect)
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: whimboo, Unassigned)
Details
(Keywords: uiwanted, Whiteboard: [wontfix?])
Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1b5pre) Gecko/20090513 Shiretoko/3.5b5pre ID:20090513034609 If the partition where the profile is located is full you will not be able to create any bookmark. That's fine. But we should catch the exception and warn the user? Steps: 1. Create a profile on an external device e.g. low capacity usb stick 2. Fill-up the usb stick with e.g. dd so no space is left 3. Start the newly created profile 4. Try to bookmark a page With step 4 the following exception is thrown and not catched: Error: uncaught exception: [Exception... "Component returned failure code: 0x80630002 [nsINavBookmarksService.insertBookmark]" nsresult: "0x80630002 (<unknown>)" location: "JS frame :: file:///Applications/Shiretoko.app/Contents/MacOS/components/nsPlacesTransactionsService.js :: PCIT_doTransaction :: line 428" data: no]
Comment 1•15 years ago
|
||
What is it supposed to do? It's probably returning OOM.
Reporter | ||
Comment 2•15 years ago
|
||
Right now the star immediately switches back to an empty star. Without any feedback. I don't think that we should confront the user with a dialog but a better explanation e.g as message in the error console would be nice?
Keywords: uiwanted
Comment 3•13 years ago
|
||
At that stage a lot of stuff would start to fail, most likely the software could even crash with oom, due to infallible allocators trying to move stuff to virtual memory. Either this becomes a general bug showing a "your disk is full" notification, or as a Places bug it's wontfix.
Whiteboard: [wontfix?]
Updated•7 years ago
|
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•