Possible bug regarding long subjects
Posted: Wed Nov 21, 2012 6:17 pmHello,
i was downloading all posts in a group earlier today, and newsbin kept crashing, but one time i noticed it was at a very very long subject line. I restarted newsbin and checked the properties of that post, and the subject was 260 chars long!
I am not sure if it is newsbin not being able to handle this (which i would find strange), but i am thinking its more of a windows filesystem related problem, i dont recall the max. path length but it is something around that, and the same with the max filename length (a limit of 255/256 would make sence in windows i think).
Anyways, i loaded up the db3 file in an sqllite browser and deleted all the posts with 255 and longer subjects - and voila, newsbin worked again.
If this IS a filesystem limitation, perhaps something should be implemented in newsbin to counter this, to either fail the file, or name it something shorter - instead of newsbin just crashing. i am not 100% sure, but i think i saw newsbin making temp files named <subject>.nb! or something like that, and that would of cause cause a problem in this situation - a numbering system based on long/int64 values would perhaps be better (eg. 100212.nb! and so forth).
My system details (and the machine does nothing else than run newsbin and an db server):
Newsbin 6.34
Windows 7 x64
Filesystem/disk setup: NTFS / RAID5 with 5 SSD's
RAM: 32GB
CPU: I7 2600K
overall i have nothing but praises for Newsbin, but this "bug" hit me a few times now...
i was downloading all posts in a group earlier today, and newsbin kept crashing, but one time i noticed it was at a very very long subject line. I restarted newsbin and checked the properties of that post, and the subject was 260 chars long!
I am not sure if it is newsbin not being able to handle this (which i would find strange), but i am thinking its more of a windows filesystem related problem, i dont recall the max. path length but it is something around that, and the same with the max filename length (a limit of 255/256 would make sence in windows i think).
Anyways, i loaded up the db3 file in an sqllite browser and deleted all the posts with 255 and longer subjects - and voila, newsbin worked again.
If this IS a filesystem limitation, perhaps something should be implemented in newsbin to counter this, to either fail the file, or name it something shorter - instead of newsbin just crashing. i am not 100% sure, but i think i saw newsbin making temp files named <subject>.nb! or something like that, and that would of cause cause a problem in this situation - a numbering system based on long/int64 values would perhaps be better (eg. 100212.nb! and so forth).
My system details (and the machine does nothing else than run newsbin and an db server):
Newsbin 6.34
Windows 7 x64
Filesystem/disk setup: NTFS / RAID5 with 5 SSD's
RAM: 32GB
CPU: I7 2600K
overall i have nothing but praises for Newsbin, but this "bug" hit me a few times now...