Compiler complains Cannot force unwrap value of non-optional type 'thread_act_array_t?.Type' (aka 'Optional<UnsafeMutablePointer<UInt32>>.Type').

For a simpler explanation, the type of the object is Optional<T>.Type which is not optional itself, as opposed to Optional<T>

Using the pod-file and updating my project given the example is fairly easy, but I'm missing instructions on how to get it running?! I tried adding the start-monitoring to my AppDelegate.swift

private func application(application: UIApplication, didFinishLaunchingWithOptions launchOptions: [NSObject: AnyObject]?) -> Bool { // Override point for customization after application launch. }

and the stop-monitoring to my AppDelegate.swift

func applicationWillTerminate(_ application: UIApplication) { // Called when the application is about to terminate. Save data if appropriate. See also applicationDidEnterBackground:. gdpMonitoringStop() }

but getting compile-errors. Do I need to add 'import GDPMonitoring' after 'import UIKit' in my AppDelegate.swift ?

Hi there, I did some minor modifications in order for the project to be Swift 5 compatible. No source changes involved. Maybe you'd be so kind to incorporate these changes back into your master repo.

Thanks Tino

Is it possible to add custom info info in the performance view?

For example, I would like to add the date when the user started the application.

Thank you a lot !

Hello, when trying to run my app with the latest GDPerfomanceView-Swift 2.1.0 on an iPhone with iOS 12.4.8 it crashes upon start at:

extension UIApplication {
    
    var keyWindow: UIWindow? {
        if #available(iOS 13, *) {
            return UIApplication.shared.windows.first { $0.isKeyWindow }
        } else {
            return UIApplication.shared.keyWindow
        }
    }
...
}

this results in an endless getter loop:

#2	0x00000001087ab9b4 in UIApplication.keyWindow.getter at Example/Pods/GDPerformanceView-Swift/GDPerformanceView-Swift/GDPerformanceMonitoring/Extensions.swift:28
...
#5309	0x00000001087abb2c in UIApplication.keyWindow.getter at Example/Pods/GDPerformanceView-Swift/GDPerformanceView-Swift/GDPerformanceMonitoring/Extensions.swift:31

resident_size does not get accurate memory, and the correct way is to use phys_footprint, which can be proved from the source codes of WebKit and XNU.Webkit Source

For cases where you don't want to call start monitoring while there is already a monitor view active.

Or at least expose a read only performanceView property...

Now that the status bar is visible on iOS 9 I recognized that the status bar style set by the view controller is ignored. My code is pretty simple:

` override var prefersStatusBarHidden: Bool { return false }

override var preferredStatusBarStyle: UIStatusBarStyle { return isDarkMode ? .lightContent : .default } `

The status bar style is switching on iOS 10 but not on iOS 9 (where it is always default).

It would be nice if this library supported interface rotation gracefully.

Currently, if I start the app in portrait and rotate to landscape, the performance view becomes centered on the top left corner.

Tested on iPhone 6, iOS 10.2

Hi, For iOS projets it's will be great to make your component Carthage compatible

Take a look at these articles:

• Ruthlessly Simple Dependency Management with Carthage
• Carthage Tutorial: Getting Started
• Making Carthage-compatible Frameworks with Swift
• Swift Cross Platform Framework (section Configure targets for Carthage) 👍

On your README.md add on top and add section for the installation with Carthage.

I've got a performance tool that similarly uses CADisplayLink to try and measure the framerate / dropped frames. But in my tests back during iOS 7 and 8, CADisplayLink's callback timing was only affected when a frame drop happened due to slowness in-process, for example if there's a lot of auto layout work. My understanding of UIKit's drawing is that after the layers are all prepared, they are composited out-of-process in iOS's equivalent of the WindowServer, as OpenGL / Metal rectangles. So if compositing is too slow, say because you have a bunch of expensive layers with blurring and rounded corners, the display link callback will still happen right on time. You'll see a slow frame rate, but the meter will show 60.

I did an ugly hack to solve this that worked in iOS 7 and 8, but doesn't work anymore in iOS 9 and 10. Did you have a way to address this? If we can figure it out, we can improve both our projects. If not, you may want to write some kind of disclaimer in your readme. :)

If you want to test this out, the repo I linked to has an example project, and you can add your meter to it. You'd want to use the ios9 branch.

The previous version contains file named GDPerformanceView-Swift/GDPerformanceMonitoring/Performance\320\241alculator.swift that prevent the build from success that showed on the attached image. I renamed it to normal. Hope that you can create a new release for it. Thank you

Hello, I have a problem on ipad, after start PerformanceMonitor, there are nothing show on screen about monitoring. This issue cause when run app on ipad without debugging mode.