[ad_1]
I am within the technique of refactoring a humongous monolithic app with a number of extensions right into a setup the place we have now a service library which is linked to every of the targets.
Nonetheless, this causes a major subject when the service library is being referenced from the notification extension, as that extension has a tough reminiscence restrict of 12MB on an iPhone 5s, which we’re nonetheless supporting, and our reminiscence utilization is at about 11MB which is manner too shut for consolation. When the reminiscence utilization surpasses the restrict, the notification extension is robotically killed by the system.
Profiling with Devices/Allocations has proven {that a} important chunk of that reminiscence is allotted (wasted, actually) by the inner AVSecondScreenController.load() class initializer from the AVKit library.
My method is now to strive to determine what causes AVKit to be loaded within the first palce. I’ve no express imports for AVKit within the notification extension and makes an attempt to determine what triggers it from the service library failed as nicely.
I did add a symbolic breakpoint for AVSecondScreenController.load() which is hit, however the backtrace is ineffective.
Does anybody have any concept how I can pinpoint what causes AVKit to be loaded within the first place?
Thanks!
[ad_2]
