aMule Forum
English => en_Bugs => Topic started by: exobuzz on April 09, 2004, 04:17:26 PM
-
I killed a copy of amule which was running and now whenever I start it I am getting
CTag::CTag(CFile*); Unknown tag: type=0x00 name=""
CTag::CTag(CFile*); Unknown tag: type=0x00 name=""
CTag::CTag(CFile*); Unknown tag: type=0x00 name=""
CTag::CTag(CFile*); Unknown tag: type=0x00 name=""
CTag::CTag(CFile*); Unknown tag: type=0x00 name=""
CTag::CTag(CFile*); Unknown tag: type=0x00 name=""
CTag::CTag(CFile*); Unknown tag: type=0x00 name=""
CTag::CTag(CFile*); Unknown tag: type=0x00 name=""
CTag::CTag(CFile*); Unknown tag: type=0x00 name=""
CTag::CTag(CFile*); Unknown tag: type=0x00 name=""
CTag::CTag(CFile*); Unknown tag: type=0x00 name=""
CTag::CTag(CFile*); Unknown tag: type=0x00 name=""
CTag::CTag(CFile*); Unknown tag: type=0x00 name=""
CTag::CTag(CFile*); Unknown tag: type=0x00 name=""
CTag::CTag(CFile*); Unknown tag: type=0x00 name=""
CTag::CTag(CFile*); Unknown tag: type=0x00 name=""
CTag::CTag(CFile*); Unknown tag: type=0x00 name=""
CTag::CTag(CFile*); Unknown tag: type=0x00 name=""
CTag::CTag(CFile*); Unknown tag: type=0x00 name=""
CTag::CTag(CFile*); Unknown tag: type=0x00 name=""
CTag::CTag(CFile*); Unknown tag: type=0x00 name=""
CTag::CTag(CFile*); Unknown tag: type=0x00 name=""
CTag::CTag(CFile*); Unknown tag: type=0x00 name=""
CTag::CTag(CFile*); Unknown tag: type=0x00 name=""
etc etc with amule using 95% of cpu and eating up my memory.
eeek
-
I see something like this reported on unknown bugs, and tagged as fixed. Although I built amule from cvs a moment ago. Are the changes not available on cvs yet ?
It's horrible having an unusable amule, and im desperate to finish off a specific download. (And don't wish to move down a version and again lose my credits)
-
Switched back to 1.2.6.
all is well again (apart from no credits again)
-
Fixed in rc2 :-)
Let us know if you have any problems on rc2. Thanx a lot!
Greetings.
-
So ppl are still haveing problems about this same message "Unknown tag: type=0x00" in v2-rc2. For those of you who can't start aMule because of it, please remove "~/.aMule/known.met".
That's the walkaround by now (until it's fixed).
I hope that helps.
Greetings