Instead of the Damn Vultures Circling My City…..

My guess is there is a memory-leak in the application which is causing HK to shut down constantly.

If you are unfamiliar with memory-leaks...when an application is ran it is given a certain amount of memory that it can consume. Each function that an application calls uses additional memory, so a leak occurs when the application doesn't release the memory and continues to use up more. An application that goes beyond the allocated memory is automatically shutdown to prevent your device from being affected.

You should work for haypi. You've told me more about why this lag happens in 30 seconds than haypi has told me in over a year

My guess is there is a memory-leak in the application which is causing HK to shut down constantly.

If you are unfamiliar with memory-leaks...when an application is ran it is given a certain amount of memory that it can consume. Each function that an application calls uses additional memory, so a leak occurs when the application doesn't release the memory and continues to use up more. An application that goes beyond the allocated memory is automatically shutdown to prevent your device from being affected.

I doubt it's a memory leak as you would see some performance degredation before the app crashes. Either way, I think everyone except Thomas and his top notch QC team agree the issues could have been found/resolved with some very basic testing of the app in a methodical manner.

My guess is there is a memory-leak in the application which is causing HK to shut down constantly.

If you are unfamiliar with memory-leaks...when an application is ran it is given a certain amount of memory that it can consume. Each function that an application calls uses additional memory, so a leak occurs when the application doesn't release the memory and continues to use up more. An application that goes beyond the allocated memory is automatically shutdown to prevent your device from being affected.

I doubt it's a memory leak as you would see some performance degredation before the app crashes. Either way, I think everyone except Thomas and his top notch QC team agree the issues could have been found/resolved with some very basic testing of the app in a methodical manner.

As I said at the beginning, they could have set up a beta game on a beta server, and not only would they have people beating down their door to play, but they would have spotted the bugs, and they would have these people on this board, and on the net crowing about how the new beta is so f%$#ing amazing.

Agreed - I made a similar comment in this thread or another, can't recall.

Just make a post in the forum "new update coming out - please contact us for participating in testing. Will be given 100 coins for your time on an account of your choice". Plenty of people will volunteer. Make up a list of things to test and allow players to report other issues also not on the "test script"......bam, month or so - most issues at least identified, if not resolved.

Common sense to me. Obviously not to Thomas, lol.

My guess is there is a memory-leak in the application which is causing HK to shut down constantly.

If you are unfamiliar with memory-leaks...when an application is ran it is given a certain amount of memory that it can consume. Each function that an application calls uses additional memory, so a leak occurs when the application doesn't release the memory and continues to use up more. An application that goes beyond the allocated memory is automatically shutdown to prevent your device from being affected.

I doubt it's a memory leak as you would see some performance degredation before the app crashes. Either way, I think everyone except Thomas and his top notch QC team agree the issues could have been found/resolved with some very basic testing of the app in a methodical manner.

Not to get too off topic, but I do notice some degradation on my iPhone right before the force quit. It doesn't happen as frequently on my iPad however as it has more memory to allocate to each app.

Without looking at the app in xCode, I can only guess as to what the cause may be. Typically this behavior is due to memory leaks, however it could be something else.

Yeah, could be. Who knows .... obviously not he Haypi developers, lmao

Agreed - I made a similar comment in this thread or another, can't recall.

Just make a post in the forum "new update coming out - please contact us for participating in testing. Will be given 100 coins for your time on an account of your choice". Plenty of people will volunteer. Make up a list of things to test and allow players to report other issues also not on the "test script"......bam, month or so - most issues at least identified, if not resolved.

Common sense to me. Obviously not to Thomas, lol.

You wouldn't even need to give out coins. The hard core would beg to try it out for free.

Agreed - I made a similar comment in this thread or another, can't recall.

Just make a post in the forum "new update coming out - please contact us for participating in testing. Will be given 100 coins for your time on an account of your choice". Plenty of people will volunteer. Make up a list of things to test and allow players to report other issues also not on the "test script"......bam, month or so - most issues at least identified, if not resolved.

Common sense to me. Obviously not to Thomas, lol.

You wouldn't even need to give out coins. The hard core would beg to try it out for free.

Granted even the most basic player could have identified these issues, Haypi should hire professional QAs. A professional would be able to give a mire in depth analysis of the stability of the application than a normal player. That's just my two cents though.

I agree completely. It is awful.