weex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From xing zhang <zhangxing610...@gmail.com>
Subject Re: WXTextComponent view crashes intermittently with EXC_BAD_ACCESS KERN_INVALID_ADDRESS in drawTextWithContext:bounds:padding:view: at _drawGlyphsForGlyphRange:atPoint:. WXTextComponent view crashes intermittently with EXC_BAD_ACCESS KERN_INVALID_ADDRESS ...
Date Wed, 13 Sep 2017 06:21:52 GMT
hi, we are trying to fix it.  It is because multi-thread draw text using
textkit,  now we are using coreText draw text,  those crashes are less.

2017-09-06 10:38 GMT+08:00 张水生 <zhang.shuisheng@immomo.com>:

> Hi, Weex Team:
>        WXTextComponent view crashes intermittently with EXC_BAD_ACCESS
> KERN_INVALID_ADDRESS in drawTextWithContext:bounds:padding:view:
> at _drawGlyphsForGlyphRange:atPoint:. This happens rarely, Harder to
> reproduce it locally. It is reported via Crashlytics often enough to be
> concerning.
>
> Here is simple stack trace:
> ===================
> Crashed: com.taobao.weex.displayQueue
> EXC_BAD_ACCESS KERN_INVALID_ADDRESS 0x0000000000000020
>
> Crashed: com.taobao.weex.displayQueue
> 0  UIFoundation                   0x195888ed4 _
> NSGlyphTreeMoveToCharacterIndex + 196
> 1  UIFoundation                   0x195889fbc _
> NSGlyphTreeGlyphRangeForCharacterRange + 84
> 2  UIFoundation                   0x19589f1f0 -[NSLayoutManager(NSPrivate)
> _drawGlyphsForGlyphRange:atPoint:] + 4512
> ====================
> I can't reproduce the issue locally, so I don't have a solution. My best
> guess is that NSTextContainer
> is being released while being drawn.
> ====================
> Weex SDK version: 0.12.0
> Platform: iOS (iOS 10 and up)
> Mac OS 10.12.3
>
> Sincerely sheng.
>
>
>
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message