I found the record

I found API record before the hangs 10:07. I saw API record at 10:03. The record not received by the app. The earliest log from the log file was 10:07.  It was sent. There is a catch but since no record for that API call, left three possibilities.

 One, the UI failed to load and not the API Anyway, I purposely put the api call there. For that button, only one so I can tell whether there is network or not. If there is, it should just redirect after receiving. The data will not be in use to load the page. It will be used several page after. 

Second, there is an image update and my app cannot find the image and hanged. Cannot be, the image was not lived. It was a menu page so nothing needed to load it except for the static link and text. 

Third, losing network just in time, i.e. before receiving the response from API. In 200 ms response that was a rare encounter but starting the first, it could be about 1 s. More chance. Hard to reproduce also. I need to turn off wifi once I click the btn. Possible? 

I have a Fourth suspect which I thought was really the app causing it. I checked back my code, there is an EXIT function after the catch so user cannot proceed if there is an error or at least until the error was solved. When there is problem Exit BUT it will only Exit after logging. There was no log so it wasn't the Exit function. I also put log if the API is successful or not successful....  If not successful, there is a pop up. None of them showed up...... These were done when loading the page. The page didn't load and no logs and no pop up but with API log record request. This is ghost. Because of number 4.

Based on these, only the windows update left and program that is not in used for about 2 to 3 days will become idle and not responsive?? Memory leak or something, or clear cache? Ok. Based on these finding, there is no issue with the code. Shit. Waste time only. Suayness.