Opened 8 years ago
Closed 8 years ago
#3556 closed Bug (No Bug)
Run, RunWait and similar calls fail with large amounts of data
Reported by: | fopetesl | Owned by: | |
---|---|---|---|
Milestone: | Component: | AutoIt | |
Version: | 3.3.14.0 | Severity: | None |
Keywords: | Cc: |
Description
I use Run() with small amounts of STDIO data and it works fine.
Another call with an expected 750+ bytes and it fails.
Examples
$DOS = Run(@ComSpec & " /c " & "echo ?DT | nc 192.168.1.6 80 > scan1.dta", "default","", $STDERR_CHILD + $STDOUT_CHILD) $DOS2 = Run(@ComSpec & " /k " & "data1.bat") $DOS3 = Run(@ComSpec & " /k " & "data2.bat") $DOS = Run(@ComSpec & " /c " & "RunDirect.exe", "", @SW_HIDE, $STDOUT_CHILD) _RunDos("RunDirect.exe")
Lines 2,3 & 4 are variations of line 1 in an attempt to provide a workaround.
There are yet another 10 variations all of which fail.
Note also Line 1 when run from a command prompt or windows explorer work 100% in all the variations.
Topic 188811 in forum refers if it helps.
Attachments (0)
Change History (3)
comment:1 Changed 8 years ago by fopetesl
comment:2 Changed 8 years ago by BrewManNH
The "bug" isn't clear at all, and your post in GH&S is even less clear. Please post the full script you're having problems with and not just tiny bits and pieces of it if you want to demonstrate a bug.
comment:3 Changed 8 years ago by Melba23
- Resolution set to No Bug
- Status changed from new to closed
You have a thread running about this problem. Wait until you actually find out that there is a bug before opening a ticket - at present I would bet on a problem with your code rather than with AutoIt itself.
M23
Guidelines for posting comments:
- You cannot re-open a ticket but you may still leave a comment if you have additional information to add.
- In-depth discussions should take place on the forum.
For more information see the full version of the ticket guidelines here.
It appears I am incorrect in indicating Run() itself is the problem.
I have discovered what causes the symptoms described above.
Immediately prior to the Run() command I have a Progress meter:
If I remove this Progress() the Run() command works and I collect 750+ bytes without a problem.
When I reinstate Progress()the subsequent Run() fails.
So the bug is clearly some interaction between the two calls.