Skip to content

[21pt] Subprocess for win32, HECRAS engine calls #324

@RobHanna-NOAA

Description

@RobHanna-NOAA

With so many HECRAS engine calls getting stuck looking for UI response, maybe we can make it a thread with a timer and a subprocess WIN32 api call to the HECRAS engine. We likely don't even need it to be a WIN32, just a straight cmd call and see if we catch the stnerr and stdout to see if we catch errors so we can can log and continue processing other units. We had yet another HUC that had so many HECRAS engine that left so many hanging processes that it mostly froze the machine. We might be able to get a newer HECRAS engine direct API call that does not even attempt to make it UI based.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions