You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I use ShowTime in one app and i really like the visual user interactions. It is very helpful for demoing features and reporting bugs via screen recordings.
The app detects if it runs on an internal test device or not (by looking for an installed other non public app which enables test mode even on release builds) and uses for non-test devices ShowTime.enabled = EnabledNever
and i expected it would then use close to zero CPU time in this case.
I run into performance issues with the app and analysed it with Instruments. I found ShowTime using more than 24% of all the app's CPU time even when disabled:
284.00 ms 24.2% @objc UIWindow.swizzled_sendEvent(_:) ShowTime
283.00 ms 24.1% UlWindow.swizzled sendEvent(:) ShowTime
Can i fix this by myself?
The text was updated successfully, but these errors were encountered:
Hey @MacMark, sorry for the mega delay (I worked somewhere that I wasn't able to work on OSS stuff so just taking a look through some issues now).
This is surprising to me because ShowTime checks if it's enabled before processing any touches, if it's not enabled it just bails out (check the implementation of swizzled_sendEvent.
Were you able to understand what part of swizzled_sendEvent is using CPU time? Might just be the swizzling of the objc runtime causing it. If that's the case then I might be able to improve it so that it only swizzles the objc stuff when enabled
I use ShowTime in one app and i really like the visual user interactions. It is very helpful for demoing features and reporting bugs via screen recordings.
The app detects if it runs on an internal test device or not (by looking for an installed other non public app which enables test mode even on release builds) and uses for non-test devices
ShowTime.enabled = EnabledNever
and i expected it would then use close to zero CPU time in this case.
I run into performance issues with the app and analysed it with Instruments. I found ShowTime using more than 24% of all the app's CPU time even when disabled:
Can i fix this by myself?
The text was updated successfully, but these errors were encountered: