线上GC异常排查

1、线上GC异常排查线上GC异常排查1现象最近去线上看了下gc情况，发现出现频繁的fullGC。问题如下图:fir阳阳WJT55555559-912335-74699999912044B7&1BElCT3CTICT3inOOOOO0757575話75巧7S7515s9111112490-808792293B73173234&29-ual81618181slel8181el8181的slslMeleln95.6835.68沾聒血95.6605沾B35.95.6895.68券点北血95.6B95,6S北血958:statCCS9.ll96.1195119.ll96.1196.1195.1196.119

2、6.1145.1196.IL95.11%1145.11%11-gcutilY5C1295BL295B12358L295E-1235E12358128561235912S59129591235912S591235912359128591295912359129591541ieeeYGCT165JB5165.765165.7B5165.?E5165.765165.765165l?E5165.776165.776165.776165.776165.776165.77615,776165.77&FGC13530513530513530513530513530513530613530S135307135

3、30713530713530713530713S3QB13530B135309135309135309135309FKT395&2.461395B2.461395B2.461395B246139562.461GCTHM取2163974B.2263974E.2263974B.22639746.3163974E.22&39583.743e?4B,B40395B3.185395E3h询539583.085395B9.ee33563.沖539563F2弼395B33T6395&3.51639563,316395B3.3K395B3J1639746r8tl3B?4B.8$13即4E冷百13974er8i

4、l30745.86139745.8=23974BJ5239749.892鶉碣上923974E.G5239749.82gc情况.jpg然后查看了下GC原因，如下:2.分析；?J2?42,?42?12M2.?J2J42?42.742?J2?42?42?12742.7J2J42.742.742.?42?Jisa11.51L3Wl&.l-?17.M勢.廿21.22.732*.牌25.7-12&.es曲.廿知.14316137.5轴.昶41.9：皈無47.1(if创Bl.5701.5761,57Bl.57Bl.H61,57B1.S7Bl.761,57Bl.=781.Bl,5701.57Bl.；7BL,5

5、7B1.E761.7Bl.57Bl.=7-1$Fl95.6895.6395.6895.SS95.6395.6895.6996.6395.6895.6S95.6395.689S.G395.6395.689S.GS95.6395.6895.63CfiRS-gtCoue1:411000佩预TFOC12期15,4941翡时91293716S.494135删129371粘.曲4135&3912期165.4941354912837IB.494135B4B13837Iffl.JW13SHB128刃165.49413541nanU5.4Mns&41120371M.49413EHL12fln165.494135

6、34113037165.494135&41120371M.4MU5H212W165.49413564213037IB.494135M31283JIM.49413S843-：gC原因图.U037165.494135943129371M.4M135M312837165.K.494135944=KT3557.639-7.6H395Z-7.61-39:.6n3-7.3S53乃軒.的5即为丁.勺茁39-7.933;-7.93?四禽.弼39Z-7.93395JB2北3951-937C39UB37(pg39:：-B37639B37(39=5&.3739:&75GGCT.(KC3S6

7、?5.1STCHSinitialllark39671.167CHSInitialHark3967ar167(USInitialHark39672.197NoOC39671.339CHSFinalRenark站阻冷御015FmalRenark39673.433CHSInitialhark39673.433CMSInitialHark396,433CHSInitioHark3067.433CMSInitialMark39673.433015InitialHark站阻订弭(USFmalRensrk39671531CHSFinal龍rsk395,364CHSIiLtialHark却W笳4(USnark

8、39673.354CMSInitialMark39&Tjr364CHSIiLtialMark396.864CHSInitioHark2；躺克.鮎斗CHSInitialMark39&7J25&CHSFutalRenarkMGCKDooOCNNNcccccccccc_cc-uGG-uG6-uHu*G-H-GG-uG6-uQOOD-OO-QOOOOOOOOONNNNNNNNXNNNNNNN根据上面两张图，可以看出主要是老年代进行了频繁的CMSGC。而CMS回收的前提条件就是老年代达到一定的容量。这个容量可以数CMSInitiatingOccupancyFraction进行设置。本项目的jvm配置如下

9、：-Xms4096m-Xmx4096m-Xmn3072m-Xss1024K-XX:PermSize=256m-XX:MaxPermSize=512m-XX:ParalleXX:+UseConcMarkSweepGC-XX:+UseParNewGC-XX:+UseCMSCompactAtFullCollection-XX:CMSInitiatingOccupancyFraction=80根据上面配置可以看出，老年代的容量为1G,且老年代达到80%的时候进行CMS回收。而根据上图可以发现老年代的占用率一直在,每次回收基本上都没有释放空间。所以一直在频繁的出发CMS回收算法。3排查依据上面的推断，使

10、用命令jmap-dump:live,format=b,file=heap.hprofpid触发fullGC,并dump内存快照。因为本次内存主要是老年代频繁GC导致的，而且每次回收都没有回收到有效空间。所以才直接加上live属性，防止年轻代对象干扰结果。然后使用mat分析内存泄漏如下：iOven/ewHIHistogram很ulistobjectsseectioriofStringBuider，ulistobjectselectionofThreadLocalJCassNaneObjectsShaowHeapstainedHeapJ0diarSS+,191674.81怖=674.81MBOja

11、va.hnglhread刚0.D9MB=630.56MB0java.lang.ThreadLocalSHireadLocalMap1,9280.04MB=63031MB9java.hng.ThreadL)calSTlirefldLocalMap$Ertry1r928024MB=63027MB=629.68MB3java.lang.StrngBuider1110.02MB=514.02MBGbyteQ112636938MB=6938MB0jawa.hng.Object35,1533.13MB=61.18MB3java.lang.Strng586,92213.43MB=5939MBGjava.ut

12、iLArrayLst31,5510.72MB=44.34MB3sun.mk.Launcher$AppClas5Lodder10.00MB=35.41MBGcombj58spat.sbdient.connmuiiication.NIOChan.40.00MB=32.00MBGjava.util.Vectcr5r3790.16MB=31.56MB0java.niQ.HeapByteEiffer4580.02MB=28.09MB芒ictir卜厂1Deel1firmFuiD_irD7heap直方图根据图中shallowheap和Retainedheap可看出占用内存最大的就是char数组。而threa

13、d、threadlocal还有StringBuilder都可能指向的就是char数组对象。下图也验证了这个猜想。5匸LlUFYIIS.UbEliLU11JIUUJCLL33CICLLIUIIUlJLlbUUIIUCLU113LUUJCl.JpCICL.IUIIUlIIKClLULnpIIIIClassName手ShallowHeapRetainedHeapjava.ang.Thread0 x788b8Z9b0SCFasyncworker26-ttiread-11ThreadO.ODME1.77MBig沁ang.Thread0 x787a97c50SCFyncworkef11-tirec-9hr

14、eadO.ODMB1.77MBjava.ang.Thread0 x783728998SCFasynuvork&r14-tliread-5HireadO.ODME1.77MB.dva.ang.Thad0 x787a968tOSCFancwofer15-tac-BhreadO.ODMB1.76MB:.ava.ang.Thad0 x787a97ec8SCFasyncztirker11-thread-2IhreadO.ODME1.76MB-%.dva.ang.Thread0 x788dbhOSCF鞠帕加6-thread-8threadO.OD1.76MB冲临ang.Thread0 x78a2OSDe0

15、SCF_a5yic_wcrker_5-thfead-10ThradO.ODME1.76MBang.Thread0 x787a9S43D5C=asyncwoer17-thread-7ThreadO.ODMB1.76MB:3j临ang.Thread(h(7879c485BSCFa&yncworker25-thread-6HireadO.ODME1.76MB肚沁ang.Thread0 x783729558SCFyncworkef17-tirec-2hreadO.ODMB1.76MB：jdva,ang.Thread0 x7879c2960SCF_a&ync_worker_30-thread-2Hire

16、adO.ODME1.76MBang.Thread0 x788bS009DSCFasyncworker30-thfead-5hreadO.ODMB1.76MB:java.ang.Thread(h(78a203BSCFa&yncworker6-thfead-8hreadO.ODME1.76MBgdva.ano.Thread0 x783728eOO5CFasvrKworker16-thread-7ThreadO.ODMB1.76MBThreadnT召习閒5=州c=giSclassjavaJang.ThreadLocalfThreddLocaMaptEntry(M0.00MBczg令ubtablevj

17、thFeadLocalsjava,angThreadLocallThreadLocalap0 x78d0a96d60.00MB匚java.ang.Tliread0 x78SbB29b0SCFasyncworker26-thrq0.00MBczg*javalang.ThreadQx788b829bOSCFasyncworkerClassNameJiOverviewNHreferentjailangJveacLew0 x7805浙400.00MBc=g令Z3gstogran也istobjectsselectionofStringBuilder凶stobjectsseiectionofThreadL

18、ocalJlhreadI9WOOOZS：kE：0?W-?I.W閱26-thread-11Thread0.00MBa23aaaXUn二二X3XRetanedHeapCJOooooCdCJOooionCdCJOooffiKThread克世stringBui-derL31学口Jdca口d0ca口Jdca口d0ca口Jdca口E3J0CQ口C3Jdca口d0ca-kH口E3Jdcai-EUdCOClassNameStriigBuiclergfe/EdDfaDaB202D-12-142035:494NFOSCF_asynmrl(i,StriigBuicler3M6feeeie202D-12-1420:3

19、2:28r936INFOSCF_asynmrk(StriigBuicler&MSdddaB202D-12-142035:30.60lNFOSCF_asynmrl(i,StnigBuicler?M3581D3&2020-12-142D:34:5?.4J9INFOSCFjcwor,StriigBuicler3fe/8a1ft6602020-12-U20:3539,32INFOSCF_acwofk,StnigBuicler3O79m2020-12-1420：a4:135NFOSCF_asynmreStringBuilderft(7BSb300682020-12-1420:33:l2r417NFOSC

20、Fjol,StriigBuicler3Md1W2020-12-1420:35:292INFOSCF_asyr(work,StriigBuicler3fe/8(iDfa3aB202D-12-1420：a4:57727NFOSCF_asynmrl(i,Stnig3uilder?fe7btaad82020-12-1420:16.089讦0CaEdtkExecutoShdlowHeapNumerio务5_?5_t至5_?另5_t至5_?另5_i至5_p另5_t至5_?另5_t至-JIc_RLJ-1Y_inv_u_nY_inv_u_nY_inv_u_nY_COLJ-IVUJ1Y_coVdetainedH

21、eapjOverview一Hili=!ke-Kf耳兰=一一Ikobjectsffiaoflcf-Th帀：】=5t&吾茗asc二目般-3s5ngBui-der-召3习11初2岗7-占邑豊一stmiS-甥Z亘匕士2S5出罢一N35刍:旨S至一已畐*口巫吕宁=寻三寻笑才7空_寸己孟7n7_v!二GFMm写二_=1SRi.EfifiWMily-WfileEditJndowijdpEthrKtclDT:DSArhgBuikki即卿“哎jjlJdddlAng5trifKulckrQ)0790124300啊占呼鼻姒啦徐斤凹血如.idvailangOflssLwderQrf?IT24CMIW.M2EJEl&r

22、4,HT3；retiredgIze阳ECrm0hijpfdr：-iDwnlewHistoqurnjIselKlIanicfsii1nn_1Isttech|转kclkmofItve_UlistcibiKhhelmlkinnlUwe.llst_dn|Kls|:CldWlMlrStdtifAlbrifc4iK-4匚IlAiHkTrch1WQjL.SiHfh直il血r炉OwWrcMdS2应D-12小120:15:06/69INFO31恥kEwnjtc/曲|4：怕讥窗7柿国仙口2$顺M21-I?-l+ajISSfeOeINFOi：llfe-：ktaei：UKii(I弗钉机pl臼呦MrimjEhilrkT

23、4).b70IJi：1?45OOSysbtr-iCImsMM-12-N20:1506iHFOI色k泌bcubor-Thnesd-pooh2J声|毗5闻XcePrldig吗)-caiAgVJF4i.u5DJu&3dnuT5l閑u田Igutli4ksy/1_501_験1：!肉q応!Ervi曲叙盘Hl护唧曲常曲电IXftIIMi.flW攸岁鶯弭7血：Vpri_ccrt3inrVI1CK1J(ZI中匕VudmthW2DlBCBrLft_prke斗需1西咛.*0Vpikfl_jVaow.irr,Vpri(e_0flt)inBYlOflW.君I曲就Tflfld罰叱，A.rrAn1-Total:2wifrl

24、ips口lalHig.Stilnldef电QKHdDr酣闘JQ2O-li-142&MS7J27INF口MF呼rM_rtv4iviIue-char|90SPCwZb119dl4fl2A2i2-l420i3529.4l2INFQ5CFkpT呂das5：|hj站&山网.InK旳日iiildfirQi7BDdf4KnTirtil:awifrlesMH!LkngStiln甲Jldtf0w阳fl曲沁闘2U2012-142(02:12,417IhtfOSt!-laveJanq.Stnng&jIrieffec7fi7Wfl%丄论H450:34:1INFO5fafynwwrier-jjmJaTa.StiingB

25、uldCTINFO&CF_Mynr_wwkQjmkna.Stiinldwft(TB35BW3B施H&M2QH59期9INFOxf&呼哦啊Hi如4巾知iftfiB.川阳矗饥7s鹹CcM閒2WO-I2-U2ft35血创I刊FO珂股g.打网心略知i啄til岭血伽7朋碍用溯屈MBI42OL322&93&INF0咒F軒中k伽虹JlaJvig.StilngBLiildcfPjewiflftlHtwpfNtFTWTJCA0.00MB1.60MB160MBCOOMBThreadLocal.ThreadLocaMap对象-threadLocal$Entry-threadLocal$Entry-StringBui

26、lder对象。有了上面的路径，就知道了内存泄漏的对象主要是在ThreadLocal中了。那么我们就需要反向从StringBuilder找到对应的ThreadLocal。排查步骤如下图:壮毗脚l炯叽卩咖加；也牌硒厕惋岡何：0酗协地曲【叩d-f曲加;:时1：浪期:斓棉换J，评;血徊側ftb?：（rt第一步找到引用StringBuilder的对象.pngJif.ddlJIL：U肌山说批Qm1-4典逍喲IlfLJ/LUMbIM:血珂删规娜题込甘広训帆M1曲第一步展示效果J：leEiKic;-ef第二步找到对应的ThreadLocalMap$Entry查看他指向的对象.png一血:的T（k苗肚*二应皿I

27、p馳皿阳肌蚯：亦询询叩血症【I珈i讣”恤血I11嗣则W协水虚：i申I萨i(krvi洌UHikOgiarrllistobjecs创Lllistcbjecis|select_llistijecissleet.Gkobjectisdect.Eiitobject!sefect.lktobertsel?CIcsNameShIcwFeap蛀加啣汽腕齢NlTlf，?J、中沁慣Im血即做曲慚帥叽蠅期园0I.J懦禅心叭网汕斓恤刑血痕屈脚业巧(诩砒CO惴肛0關第二步展示效果1恤的牌刖帕世曲!哪:曲郦上魏鰹地1鼻百Fk绊百INuiiierk=NuffiericLijitw.lnngThrELcoIRhi咖lUxMM

28、nME肺y騎銅?卿QOOMB击押足旧.|0叩1商歸1|_0饲恬ThfeadLo询lyiapTE时ry(Is(州6aE000MB0.00MBjaraldriq.rer.ReclassJjvaJangJhreiLacal卷0 x7Scl8MJ0SystiljraiwoiavaJang.SirirBuilder睜OK7U2eccadB203SK12-142C工g|*rrt曲nnnhjRLktobjrchiShowDbirctEbycImghPathToGCRoatEEMergeShcflMilPAlhcIoGCRoatiBasicsLeakldenlikatkPEKpalSfU0&lv3*Immed

29、iateDnilortShamRetainedSetC-referaitjava,週JheMkxa$lte0LodM碱Entry0 x783211190ShiouvHeapRetainedHeap0.0DMB0.00Mb-referentava.迥血抽；亦t珈LowMapfEitry3Ox底胁她oODMB129MB-referentava.迥IheM恥伽囱讹5MapfEitry?加8熾5cfBQODMBIBMb-referentava.迥血抽；亦t珈LowMapfEitry31加832012題oODMB0.00MB-referentava.迥IheM恥伽囱讹5MapfEitry?血底4倂68Q

30、ODMB100Mb-referentava.迥口血恥阮t珈LowMapfEitry31加8344MMoODMB153MB-referaitjava,週JheMkxa$lte0LodM碱EntryOx78M)608QODMB129Mb-referentjava.迥IheM血北Tt珈应测斛Eitry31加83440瑚uODMB0.80MB-referaitjava,週JheMkxa$lte0LodM碱Entry加8344哦QODMBIUM&-referentjava,眄.Th旳dka$ltedLodM碱Entry0 x7834411e8oODMB153MB-rpfArPdt仙smThrpfld旳1

31、灯hsrlln柑MantFnirv御fly?AWWRnnnmr1兀MR第三步效果图步骤描述：右键某个StringBuilder对象，选择listobjects-withincomingreferences（也就是找到指向当前StringBuilder对象的对象）打开引用链，找到引用当前StringBuilder的ThreadLocal$ThreadLocalMap$Entry对象。然后右键，选择listobjects-withoutgoingreferences（找到ThreadLocal$ThreadLocalMap$Entry对象引用的对象）找到当前ThreadLocal$ThreadLo

32、calMap$Entry对象的属性，referent属性，右键listobjects-withincomingreferences（因为ThreadLocal$ThreadLocalMap$Entry类继承了弱引用，其中的threadlocal对象就是在referent属性中。所以此步骤是找到指向threadlocal对象的所有引用）因为指向threadLocal的对象较多，所以需要排除很多ThreadLocal$ThreadLocalMap$Entry对象，最终我们找到了哪个我们期望的引用org.apache.logging.log4j.core.layout.AbstractStringL

33、ayout4代码分析接下来查看代码AbstractStringLayout。通过查找发现，我们这个类属于log4j的。查看代码发现threadLocal就是在这里使用的2，30*httE?5；f/i号sug刍，羽耳匸眩。早fjirmfbrpwsefLO54J2-9第fordetails539rji：public,abstiactcl-sssWbstract5cnngL*youtKt-edsAbacraccLsyoutiiipl-eiientsScncgLoutAlFsGefaMtletihforne*r5iringffalderinsTanres./tfvjrJwF.44*/procecced

34、staticfi/iaLintDfJLtJL5rf.W_FLTLDfK_5IZf-1324：4T1privatefinalstatii:ThreadLocalStringSuiIder-?*(占厂農i3*acjij!n=ThreadLDcali):dqprivatestaticfinalserjal?ionUIfls1L;threadlocal引用地址而代码中threadloca使用到的地方只有下图这个地方:W31艇*returnaStringSuilder105i1瞒protetitECString0LiLdergetStringEiuilder()W7StrirgBuilderresult

35、=trreaosal.get:ioeifCresultniL109result=的StringEuilder(MLrSIRIAGBUILDERSIZE);1WthreadLocal.set(restIti:111112result.setLengthfST:B3_.threadlocaI使用的地方通过断点发现，日志打印的时候，会先在StringBuilder中生成，而StringBuilder是存在于当前线程中的。每次打印新的日志的时候，都是调用下result.setLength（O）方法，将原有的日志内容置空。而StringBuilder的这个方法，只会count指针置为0,实际并不会释放S

36、tringBuilder内value占用的内存。所以才导致了内存的泄漏。（这里强调下，本项目使用的log4J的版本是2.5）5解决问题发现了问题就很容易解决了，通过查询，只需要将log4J升级即可解决这个问题（没有挨个查看具体是那个版本解决的，但是就遇到过的2.8.2已经解决了）。本项目直接使用了2.13.2先来看下解决之后的效果吧。1.内存使用率6：2020-12-21n29:0810.144.11755:59355K2020-12-21巧四0010.HU6a.202:5952%2020-12-21n29:0010.14S.64.H6:59925K2020-12-21n29:0010.lM.

37、ffi.22l:砸I4：gc内存占用率修复前.jpg2，2，12-2116:0312-2208CO16:0012-2316:0C30604020MCQ-12-23H:1UO1:I44.1K95:52.25KMCQ-12-23H:1UO1:II45.B:202:5275KKGQ-12-23HzlUO1:II45.&4.H6:52.66KKGQ-12-23HzlUO1:I44.6i.22:T.I為gc内存占用率修复后.jpg根据上面两张图,2.cpu使用率可以看出来修复前后差不多差了百分之7%左右，而内存总量为8G,所以前后相差差不多560M左右。gc前后cpu占用情况.jpg根据上图可看出,3.

38、gc情况修复前cpu使用差不多为18%左右，修复后为4%左右，前后相差14左右，效果还是很明显的5jftltcutit1M31M051ctaiCCS论TOCTFGCFGCTOCT心日剧47,S9.4S蚁5站7.SE1D3.6218.4221=.G3B.6952.1239.S3954S96.IB5307.8E158.EH3.422I1们5：7233.E&96.ie5沖7.8E1&9.6213,4221心53ja3S.E&眄.轴ss.ia5307.8E1：9.621&,4竝1/的5：6039.ca954S96.185=07.8E159.E21B.4391E.03乩阳se.ii躬點85曲7.SC15

39、521B.4221.032.E&se.739.ea.48S3&7.8E1：0.5218.4221丽0.G9siei39.E8954896.185=07.8G159.5213.U21乩阳61.5533.E&的轲%.ie河7.8E1&3.EH8*4221旳2.E&.ia39.ea$5,489$.iaS3&7.8E1D9.621a.4221S.G3O.EO64.6533.es954896.IB5=07.SE1s3.5218.43213,E966.6539.&的轲96.ie5307.891&3.sn3,4221旳2.E9J,G939.ES眄48鲂,1$5307.fiEl:9,6Ua.4221们0.G5

40、69.639.G&954S96.ia5=07.8C13.S218.4391E.03S.E971.5731黑护4896.le5207.8G1521B.4221旳2.972.013乩E854?$.laS3&7.8E1：9.5218.4221丽0.G971.5B33M95.4496.185307.8G159.6213.U211D33,0974,e$翦.E8羽轲?6.ie5307.6&1&9.621S.422H_&中_q曲ru0尺Aftmi*_7API_I_AE_4Egc修复之后.jpg3S1AuooQ妙o0协SQSaSSCSSCG0朋51：2B52.0732.2652.9253.435斗，3154,

41、7555.56.6757,5353.9761.9462.66&3.MS4.B55.2E55.5Z67.BB6S.$2sS:1,1541.15M5.阳.95.轴.95.95195.阪55.M.95.55.95,95.55.泊.95,95.696.0196.01则M96.61軸血96.0196.01帕Ml5S.01骑忌96.019氣0196.01怕Ml弼血9,9196上196b019S.01$g.ei沾月J9g,0196.01旳匚1Q45104&16451B45104510451Q4514S104519451D451.6451045194S1B4S1045104516451B4

42、S194S16451B451045-TGCTL马円MIA1914.919141L叫邓14.191414.19田14.919雷用沖14.19L49Ml百占均皿邓114,9114-eis14.919141514.91S14r19FOCTii1111111222J-2A-s-&$OCTLGCC15-539OlocationFiiTur#15.539ftlloiationFailure13-539AllocationFailure9iLllocatiDnFailure15.539AlldeAtianFtilurA15.39AllocationFailure15-539A.IlocationFiilur

43、*15.539AllocatioftFailure15.539Ul1)/LOG4J2-2368/RecursiveloggingmayclobberthecachedStringBuilder.returnnewStringBuilder(DEFAULT_STRING_BUILDER_SIZE);StringBuilderresult=threadLocal.get();if(result=null)/初始化StringBuilder的长度为1024result=newStringBuilder(1024);threadLocal.set(result);/主要就是这里进行了缩容trimToM

44、axSize(result);result.setLength(0);returnresult;333最主要的改进就是上面的trimToMaxSize方法，再看下这个方法:/AbstractStringLayout的方法protectedstaticvoidtrimToMaxSize(finalStringBuilderstringBuilder)1024);/StringBuilder勺方法publicstaticvoidtrimToMaxSize(finalStringBuilderstringBuilder,finalintmaxSize)stringBuilder.setLength(

45、maxSize);/金融StringBuilder中去进行缩容stringBuilder.trimToSize()publicvoidtrimToSize()/这里就是具体的缩容了if(countN4UKiHI2+Mi：刃MMIIKHI7I3WI：if(stringBuilder!=null&stringBuilder.capacity()maxSize)eMHKiS-iHWKiMrfIhlfCIhlRblKi：*iaiKI9333HKi/这里还有可能不设置属性，取到2048/第二个参数的获取，是根据这是的og4j的属性log4j.layoutStringBuilder.maxSize和1042取较大值LJ叩7.叫91叫2jjb-J.M-VK*=IMiwllSkXJIEJdliuCUKJuM-|tKilZ4*X!：i416|nruWir3iUi3?kl.nF-MriiM|3Liiilti理列空LJHAaeSm:I4I3M-JWI2Lid!-WijiK|-.l5HC|2raKa2iliiix-T-.Hmcid-iaiiktaEi：2B5IH-r：ltKll42L7K!古XT