User Tag List

  1. <Ian Nicoll/>'s Avatar
    Running a CPU at high % (70 - 100) isn't all that strange & won't do any harm if the cooling system is adequate.

    It's documented everywhere about big memory leaks in UIWebView, just google it. No need to post proof here. Fact is it's been like this for years!

    So I believe the biggest factor is iOS8, it won't even run on iPh4, & runs very poorly on iPh4S, so do the maths, iOS8 + UIWebView memory leaks + very high screen resolutions = memory top-out.

    iPh5 - smaller screen resolution = less memory usage but still very high, just not high enough to cause too much issues.

    iPh6 - larger screen resolution = more memory usage than iPh5 occasionally topping out at 100% (depending on animation amount & the amount of other tweaks being used) giving the odd respring.

    iPh6+ - huge screen resolution = a lot more memory usage so tops out to 100% very easily - constant resprings.

    JMO.

    @ Boots,
    I apologise for Krima's comment, what he meant to say was:
    "Please shut it woman, men are talking".
    So all good now eh? Oh, & woman, us men need beer.

    You can't drive to my house LOL.
    Last edited by <Ian Nicoll/>; 2015-03-06 at 08:26 AM.
    2015-03-06 12:32 AM
  2. Kristatos's Avatar
    Ian, thanks a lot for your help...worked great!...

    UniAW7-imageuploadedbymodmyi1425605366.970497.jpg
    2015-03-06 01:29 AM
  3. King_O_Hill's Avatar
    I gotta say that I think my money's on Boots too!

    Check out WW3 for iOS 9/10 - Widget-Weather 3.0
    2015-03-06 01:50 AM
  4. Boots's Avatar
    u buys the plane ticket ian and ill gladly bring ya some beer!
    and thanx for correcting krimas comment...that Please made all the difference! hahah
    2015-03-06 01:52 AM
  5. NewD's Avatar
    Running a CPU at high % (70 - 100) isn't all that strange & won't do any harm if the cooling system is adequate.

    It's documented everywhere about big memory leaks in UIWebView, just google it. No need to post proof here. Fact is it's been like this for years!

    So I believe the biggest factor is iOS8, it won't even run on iPh4, & runs very poorly on iPh4S, so do the maths, iOS8 + UIWebView memory leaks + very high screen resolutions = memory top-out.

    iPh5 - smaller screen resolution = less memory usage but still very high, just not high enough to cause too much issues.

    iPh6 - larger screen resolution = more memory usage than iPh5 occasionally topping out at 100% (depending on animation amount & the amount of other tweaks installed) giving the odd respring.

    iPh6+ - huge screen resolution = a lot more memory usage so tops out to 100% very easily - constant resprings.

    JMO.
    Yeah, Ian.. That was also my conclusion in the beginning.. But I was assured by many principle intellects here (King, Krima, RKO, Simon) that there was no proof of any RAM leakage in UIWebview in iOS8 - despite even Apple's own release notes. I took quite a verbal beating on many fronts for my 'belief' in the RAM leak.. Once 'beat down'.. I went looking elsewhere for an answer.. IF, there is a RAM leak in UI - that would indeed explain alot very logically for me.. and it means that 2GB of RAM won't solve the issue if UI still has leaks in iOS9, as a leak will eventually deplete any supply of RAM.

    I do see the RAM part of the equation the more we discuss it... IF a leak is what's happening with UIWV. But I also know a depletion of CPU will cause a respring.. So let's just hope iOS9 or even 8.3 gives us some hope.. And thank goodness for WKWebView which dispels the resprings even in 1GB of RAM.

    Thanks for your thoughts, m8...
    Last edited by NewD; 2015-03-06 at 01:57 AM.
    2015-03-06 01:55 AM
  6. #m37h{'s Avatar
    i think i am done for tonight

    2015-03-06 02:33 AM
  7. Wayne Ross's Avatar
    My first mod (all thanks to all of you guys)... It is pretty basic, but I am far from done. My next step is to get that Delorean code working, any assistance would be greatly appreciated.UniAW7-imageuploadedbymodmyi1425617436.658913.jpg
    GET SOME!!
    2015-03-06 04:50 AM
  8. Best01's Avatar
    Hey guys can some please remind me how to change date from 5 March to march 5th on 7.1. Tia
    2015-03-06 05:02 AM
  9. Pibe77's Avatar
    Hey guys can some please remind me how to change date from 5 March to march 5th on 7.1. Tia





    Inviato dal mio iPhone utilizzando Tapatalk
    2015-03-06 05:08 AM
  10. Best01's Avatar
    Thank you very much
    2015-03-06 05:15 AM
  11. Pibe77's Avatar
    Thank you very much
    No problemUniAW7


    Inviato dal mio iPhone utilizzando Tapatalk
    2015-03-06 05:17 AM
  12. Platini2000's Avatar
    Have a nice day all..
    2015-03-06 05:45 AM
  13. <Ian Nicoll/>'s Avatar
    Yeah, Ian.. That was also my conclusion in the beginning.. But I was assured by many principle intellects here (King, Krima, RKO, Simon) that there was no proof of any RAM leakage in UIWebview in iOS8 - despite even Apple's own release notes.
    Like I said it's JMO. It could also be the way the dev's are coding the LS players, seems url requests (which they use for loading our html files) in UIWebView are an issue, something about it never releases the memory used, i.e if you load the url a 2nd time it doesn't release the memory from the first load, it's all over the net & seems very common but there is also loads of advice on how to fix it.

    massive memory leak in ios UIWebView - Stack Overflow

    Obviously we can't try these things out cause we're not the developers.
    Dammit I haven't learned anymore Objective-C for months now.

    Whatever the issue, WKWebkit/View seems to be the answer, what can we do?
    Last edited by <Ian Nicoll/>; 2015-03-06 at 09:37 AM.
    2015-03-06 09:12 AM
  14. <Ian Nicoll/>'s Avatar
    My first mod (all thanks to all of you guys)... It is pretty basic, but I am far from done. My next step is to get that Delorean code working, any assistance would be greatly appreciated.UniAW7-imageuploadedbymodmyi1425617436.658913.jpg
    Use my old instructions, ignore any iph4, 5 & 6 stuff, in other words, just pretend you have iph6+.
    Maybe later I will work our the % values.
    2015-03-06 09:14 AM
  15. Simon's Avatar
    Yeah, Ian.. That was also my conclusion in the beginning.. But I was assured by many principle intellects here (King, Krima, RKO, Simon) that there was no proof of any RAM leakage in UIWebview in iOS8 - despite even Apple's own release notes. I took quite a verbal beating on many fronts for my 'belief' in the RAM leak.. Once 'beat down'.. I went looking elsewhere for an answer.. IF, there is a RAM leak in UI - that would indeed explain alot very logically for me.. and it means that 2GB of RAM won't solve the issue if UI still has leaks in iOS9, as a leak will eventually deplete any supply of RAM.

    I do see the RAM part of the equation the more we discuss it... IF a leak is what's happening with UIWV. But I also know a depletion of CPU will cause a respring.. So let's just hope iOS9 or even 8.3 gives us some hope.. And thank goodness for WKWebView which dispels the resprings even in 1GB of RAM.

    Thanks for your thoughts, m8...
    Memory is failing you a little old timer
    We didn't debate that there wasn't memory leaks. We were debating that memory leaks were fixed in 8.1 updates meaning our respring issues would be helped. You seemed to think they were based on apples change notes.

    None of us ever said to you there are no memory leaks.
    2015-03-06 12:08 PM
  16. Simon's Avatar
    But I also know a depletion of CPU will cause a respring..
    You know this based on what?
    2015-03-06 12:13 PM
  17. <Ian Nicoll/>'s Avatar
    "Depletion of CPU" is possible, but I don't think you would be alive to see it, I mean if your cooling is ok, it takes decades to depreciate, for sure it will outlive it's usefulness.
    Last edited by <Ian Nicoll/>; 2015-03-06 at 12:56 PM.
    2015-03-06 12:24 PM
  18. NewD's Avatar
    Memory is failing you a little old timer
    We didn't debate that there wasn't memory leaks. We were debating that memory leaks were fixed in 8.1 updates meaning our respring issues would be helped. You seemed to think they were based on apples change notes.

    None of us ever said to you there are no memory leaks.
    Incorrect, bro. That 8.1 had fixes for the memory leaks was a different debate, bro. I took a beating there too. But I took an initial beating for the memory leaks themselves.. When I reposted the Apple links it calmed down.. But I have the scars from the original besting too. UniAW7.. At least Apple's release notes for 8.1 were proof of the leaks in 8.0 - but before 8.1 there was no proof and I was most definitely "challenged" UniAW7..

    As to CPU depletion I remember seeing a Crash Reporter error showing it on my phone.. if memory serves.. But I know what you think about my memory.. UniAW7UniAW7 I will do some more reading up on this to make sure I'm educated on the topic.
    Last edited by NewD; 2015-03-06 at 12:54 PM.
    2015-03-06 12:43 PM
  19. Simon's Avatar
    Don't remember ever saying there are no memory leaks. Krima/King/RKO you guys remember saying that? Closest thing to that I remember is the apple notes on the update and what they fixed. We differed in our understanding on what those notes meant, corruption vs leak I think it was. This was all part of the same debate. There weren't two separate debates on this from what I remember.
    There may well be memory leaks in iOS 8. There might not be. I don't know for sure either way. I just know my interpretation of what apple fixed in 8.1 wasn't proof a memory leak existed pertaining to our resprings and was fixed. I do know it didn't fix our resprings.
    2015-03-06 12:57 PM
  20. Krima's Avatar
    My memory of that fantastic discussion is more along the lines of Simons. We differed on corruption vs leak and if this had any issue with resprings.

    I remember the usual demanding proof, giving said proof, and then someone saying that isnt the proof he wanted because it hasn't been notarized.
    2015-03-06 01:09 PM
LINK TO POST COPIED TO CLIPBOARD