Project

General

Profile

Bug #2250

Crash on launch when trying to index folders with lots of files, or files with unexpected names/content

Added by skyjake about 5 years ago. Updated over 3 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Defect
Target version:
Start date:
2017-06-19
% Done:

100%

Tags:

Description

The file system indexer may have a bug when reading some files and/or folders.

See discussion: http://dengine.net/talk/discussion/2452/fresh-install-doomsday-2-0-1-crashes-instantly/p1


Related issues

Related to Bug #2225: Some packages are not displayed in package list until tricky editing info fileClosed2017-04-01

Associated revisions

Revision 8ea5f631 (diff)
Added by skyjake about 5 years ago

Fixed|Resources|libdoomsday: Avoid certain characters when choosing package IDs

Some characters have special meaning in the context of package IDs.
For instance, whitespace characters are used as list separators by
PackageLoader. Also, Info strings are ambiguous if there are lots of
consecutive single and double quote characters, so those are replaced
as well.

IssueID #2250

Revision 8f1b41b4 (diff)
Added by skyjake about 5 years ago

Fixed|Resources|libdoomsday: Avoid certain characters when choosing package IDs

Some characters have special meaning in the context of package IDs.
For instance, whitespace characters are used as list separators by
PackageLoader. Also, Info strings are ambiguous if there are lots of
consecutive single and double quote characters, so those are replaced
as well.

IssueID #2250

Revision bd9ab716 (diff)
Added by skyjake over 4 years ago

FS|libcore: Added option for disabling multithreaded file system updates

To help diagnose file system crashes, a new option was added that
disables the multithreaded folder contents population.

In ~/.doomsday/defaults, add:

fs { multithreaded = false }

IssueID #2250

Revision 4b7de994 (diff)
Added by skyjake over 4 years ago

FS|libcore: Improved "fs:multithreaded" option

Notification about completion should only occur at the end of a
tree update.

IssueID #2250

History

#1 Updated by skyjake about 5 years ago

  • Status changed from New to In Progress
  • % Done changed from 0 to 30

#2 Updated by skyjake about 5 years ago

  • Related to Bug #2225: Some packages are not displayed in package list until tricky editing info file added

#3 Updated by skyjake about 5 years ago

  • Target version changed from 2.0.2 to 2.0.3

#4 Updated by skyjake almost 5 years ago

  • Target version changed from 2.0.3 to 72

#5 Updated by skyjake almost 5 years ago

  • Target version changed from 72 to 74

#6 Updated by skyjake almost 4 years ago

  • Target version changed from 74 to 72

#7 Updated by skyjake over 3 years ago

  • Status changed from In Progress to Resolved
  • Target version changed from 72 to 2.1 (Late 2018)
  • % Done changed from 30 to 100

The likely cause for this was that multiple threads tried to initialize the data bundles registry simultaneously: 0c5600189282404

#8 Updated by skyjake over 3 years ago

  • Status changed from Resolved to Closed

Also available in: Atom PDF