aaron kulkis cmiqlkx91hotpopcom peter nikolic wrote thursday 14 february 2008 per jessen wrote greg freemyer wrote per dont know measured load important measure short power surges particular im suspicious load raid1 resync could technique catch 10 msec spike etc nope chance see reply carlos think spikes causing trouble sata drives dont know know new power supplies major source error reports lkml last year extremely routine even new 650w supplies interesting sata drives causing problems far system still less stable load per jessen zürich made certain good thermal connection cpu heatsink sounds like problem machine turned need cleanup new thermal compound reseat heatsink problems since might worth look one spec dust fractionally big could cause untold hassle dont use godawful thermal putty use good thermal grease like zalman zmstg1 arctic silver arctic silver 5 arctic silver ceramique way greases designed slight vibration fan heat sink slowly push larger particles larger gaps thus optimal heat transfer cpu heat sink happen initially take couple weeks zalman 2x price typical silverbased grease comes nice bottle fingernail polish brush cap apply nice even coat across surfaces without ending excess oozing place dlnirllcwaikatoacnz sun feb 24 103011 2008 message 5 date wed 13 feb 2008 091252 1300 peter reutemann subject wekalist ripper algorithm pruning weka machine learning workbench list messageid 47b1fdc43000102waikatoacnz contenttype textplain charset3diso88591 format3dflowed saw version 334 also latest jrip uses fastvector whe n saw running weather nominal data 14 rule two conditio ns humidity 3d high outlook 3d sunny pruning rule calls fastvectorremoveelementat1 causes size reduced objects still held ie antecedents remov ed object even though size reduced 1 look vector co de public final void removeelementatint index systemarraycopym_objects index 1 m_objects index m_size index 1 m_size see object size reduced m_objects still two ripperr ule objects debugged using eclipse debugger someone explain bug something missing noticed already m_objects array still contain number objects take closer look debugger notice two last objects reference since m_size got reduced possible access last object anymore outside calling code element removed theres one problem see approach one deletes least one element start least two references last object last object gets removed still references array object garbage collector likely never claim removeelementat method set last object explicitly null imho cheers peter peter reutemann dept computer science university waikato nz httpwwwcswaikatoacnzfracpete 64 7 8384466 ext 5174 tue 05 aug 2008 033700 0500 opensuse ot much power pc really consume