Except that the same check led to a situation where something unintentional was shared. This was with an old version of LinuxDC++ (0.691 I believe) and required some character encoding changes between 2 executions.
I didn't manage to reproduce the effect with 0.75 core though, but don't know if it is because I don't remember the steps correctly or because other changes in the hashmanager code. But yes, it can hurt to check (of course the other option was a crash in that situation, you decide which is more painful). --RZ -- out of memory if share contains broken directory names https://bugs.launchpad.net/bugs/300728 You received this bug notification because you are a member of LinuxDC++ Team, which is subscribed to LinuxDC++. Status in DC++: Confirmed Status in Linux DC++: Confirmed Bug description: linuxdcpp-1.0.2 Filesystem: ext3 utf8 Default hub encoding: CP1251 (Cyrillic) All works fine until I create on share directory with name in broken encoding. Linuxdcpp eat all memory (RSS size more than 700 mb) and killed by OOM. _______________________________________________ Mailing list: https://launchpad.net/~linuxdcpp-team Post to : [email protected] Unsubscribe : https://launchpad.net/~linuxdcpp-team More help : https://help.launchpad.net/ListHelp
