Re: [lwip-users] Connection abort due to max SYN retries reached

2017-03-23 Thread goldsimon
After looking at the changelog, I also guess it must be your test. What's changed there is that slowtmr checked for == max retries and I've changed it to >=. The old code had the assumption that nrtx was increased in the timer only, but in SYN_SENT, it is increased asynchronously as well.

Re: [lwip-users] Connection abort due to max SYN retries reached

2017-03-23 Thread D.C. van Moolenbroek
Hi, On 3/22/2017 18:11, Axel Lin wrote: I recently found it's easy to get connection abort when I test connecting web server. (test by just repeating send http request) It's easy to get below debug message: tcp_slowtmr: max SYN retries reached Just a guess: could it be that your test is

Re: [lwip-users] heap problem with chrome

2017-03-23 Thread Mohamed Hnezli
I did, currently I am working on an other task in parrallel, so I'll try it later, thank you a lot On 22 March 2017 at 17:05, goldsimon wrote: > > > Mohamed Hnezli wrote: > > what makes me confused > > is that there is no problem with firefox > > Did you read my mail you