Open
Bug 193641
Opened 22 years ago
Updated 2 months ago
investigate 'FastLoadFileWriter stream left open for indefinite periods ?'
Categories
(Core :: XUL, defect)
Core
XUL
Tracking
()
NEW
mozilla1.4alpha
People
(Reporter: jrgmorrison, Unassigned)
Details
Attachments
(1 obsolete file)
investigate 'FastLoadFileWriter stream left open for indefinite periods ?' Seems that it doesn't always close at the end of a fastload episode. Cases: at startup, fastload file either exists or it doesn't; if it exists, it may not be valid. If it is valid it may or may not contain some (or all) of the serialized content required by the current episode. Also, multiple master documents may affect the handling. [Instrument/assert the fastloadset put's and remove's].
Reporter | ||
Updated•22 years ago
|
Status: NEW → ASSIGNED
Target Milestone: --- → mozilla1.4alpha
Reporter | ||
Comment 1•22 years ago
|
||
Seems that it is the reader that is not closed. If a document exists in the fastload file, it, of course, never enters enters WritePrototype, which is where the logic to close streams (and release fastload service and file) exists. Maybe we just need to set up equivalent code that the reader will execute.
Component: XP Toolkit/Widgets: XUL → XUL
QA Contact: shrir → xptoolkit.widgets
Comment 2•2 years ago
|
||
The bug assignee didn't login in Bugzilla in the last 7 months, so the assignee is being reset.
Assignee: jrgmorrison → nobody
Status: ASSIGNED → NEW
Updated•2 years ago
|
Severity: normal → S3
Comment hidden (spam) |
Updated•2 months ago
|
Attachment #9386371 -
Attachment is obsolete: true
You need to log in
before you can comment on or make changes to this bug.
Description
•