When running curl_race.exe in a long sequence here, I don't see any problem.
But in run_many.bat you start so many processes in parallel that you hit
this problem. Buffer/stack overflow, starved Winsock buffers, runtime DLL
limits etc.
I am not sure if you are speculating or if you were able
Tom K. li...@citizenkeen.com wrote:
How would a different compiler rule out libcurl?
I'm just suggesting that GNU C++ is a better compiler than MSVC++.
PS. In the project-file I saw you did use '-D_SCL_SECURE_NO_WARNINGS'.
Why?
This is fairly common practice with MSVC, whether good or
I've an update, hopefully this can get us closer to a resolution.
When everything locks up as you say, does the machine really stop working
or is there network traffic still going on?
Traffic does cease, it is unresponsive to RDP/remote debugging. I
can't even force the OS to bluescreen via
Tom K. li...@citizenkeen.com wrote:
https://github.com/tomisarobot/curl_race
This example creates a CURL handle and then sends data in a loop. I
start 200 of these applications up and eventually the system will
become unresponsive to the point of having to press the power button.
When
I have an app that sends via libcurl on a background thread. I run
200 of this app on a windows7 machine. They aren't all sending at
once, though the producer thread is waking on frame intervals, so its
possible that many try and do work at the same time.
When the endpoint is reliable, this all
On Mon, Feb 18, 2013 at 11:35:16AM -0600, Tom K. wrote:
I have an app that sends via libcurl on a background thread. I run
200 of this app on a windows7 machine. They aren't all sending at
once, though the producer thread is waking on frame intervals, so its
possible that many try and do
Hopefully this isn't a duplicate, I don't know what my email client is doing.
Have you read and followed
http://curl.haxx.se/libcurl/c/libcurl-tutorial.html#Multi-threading ?
Each process has only one thread which accesses its own curl object,
so I believe that obviates the advice in the link.
On Mon, 18 Feb 2013, Tom K. wrote:
When the endpoint is reliable, this all works fine. When it is not
reliable, it will lock up the system. Not immediately, though usually
within 10 minutes or so.
200 is not a very large amount though. I've personally done 10K connections
with libcurl and
When everything locks up as you say, does the machine really stop working
or is there network traffic still going on?
I fairly sure that all traffic ceases, though I will double check.
The box sounds like it has power, I get no events in the event viewer,
no crash dump from the OS. I interpret
