Timeline for RunProcess vs. Run - cpu usage
Current License: CC BY-SA 3.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 20, 2017 at 7:34 | comment | added | Turgon | Confirmed on Windows 10, mma 11.1; CentOS, mma 11.2. | |
| Oct 13, 2017 at 11:26 | history | edited | Szabolcs | CC BY-SA 3.0 |
added 100 characters in body
|
| Oct 13, 2017 at 8:59 | history | edited | Szabolcs |
edited tags
|
|
| Oct 13, 2017 at 8:10 | comment | added | image357 | @Szabolcs: Yes I did. The report was forwarded to their developers. I'll post an answer when the issue is resolved. | |
| Oct 13, 2017 at 7:57 | comment | added | Szabolcs | Did you report this to Wolfram Support? If you haven't, please do so, and let us know what they said. It smells like a bug to me. | |
| Oct 10, 2017 at 20:49 | history | tweeted | twitter.com/StackMma/status/917854542175272960 | ||
| Oct 10, 2017 at 15:31 | comment | added | Szabolcs | Confirmed on OS X too. | |
| Oct 10, 2017 at 15:30 | answer | added | george2079 | timeline score: 6 | |
| Oct 10, 2017 at 15:12 | comment | added | george2079 |
I can confirm this. redhat/mma11.1. RunProcess connects to the process stdout , while Run does not. I don't see why that should take so much cpu though.
|
|
| Oct 10, 2017 at 14:38 | history | asked | image357 | CC BY-SA 3.0 |