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

2017-03-22 Thread goldsi...@gmx.de
Axel Lin wrote: It's easy to get below debug message: tcp_slowtmr: max SYN retries reached I tried increase TCP_SYNMAXRTX but it seems does not help. Hmm, we have changed something around there in 2.0.2, could you check how 2.0.1 behaves? Simon _

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

2017-03-22 Thread Axel Lin
Hi, I'm using netconn API and running with FreeRTOS. When test my application with current lwip git tree. 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 retr

Re: [lwip-users] heap problem with chrome

2017-03-22 Thread goldsimon
Mohamed Hnezli wrote: > what makes me confused > is that there is no problem with firefox Did you read my mail you replied to? Simon ___ lwip-users mailing list lwip-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/lwip-users

Re: [lwip-users] heap problem with chrome

2017-03-22 Thread Mohamed Hnezli
Hi Naom, Thank you for aswering, that's usefull On 22 March 2017 at 11:45, Noam Weissman wrote: > Hi, > > > > I am not familiar with netconn API but I will try.. > > > > Every browser implements the protocol a bit differently. The data fields > in the HTTP may not be > > In the same order and so

Re: [lwip-users] heap problem with chrome

2017-03-22 Thread Noam Weissman
Hi, I am not familiar with netconn API but I will try.. Every browser implements the protocol a bit differently. The data fields in the HTTP may not be In the same order and sometimes (IE) are very long… That leads to problems when your code Is very optimized and unexpected. I found that on th

Re: [lwip-users] heap problem with chrome

2017-03-22 Thread Mohamed Hnezli
hello again, I am using HTTP server example using the netconn API, I have a strict memory constraint but what makes me confused is that there is no problem with firefox On 21 March 2017 at 18:44, goldsi...@gmx.de wrote: > Mohamed Hnezli wrote: > >> when reloading a tab in chrome or adding new o