Fix the OutOfMemory exception reporting

CommonWealthRobotics / BowlerStudio

A Full-Stack Robotics Development Environment

GNU Lesser General Public License v3.0

129 stars 29 forks source link

Fix the OutOfMemory exception reporting #326

Closed madhephaestus closed 1 year ago

madhephaestus commented 1 year ago

https://github.com/CommonWealthRobotics/BowlerStudio/issues/145

madhephaestus commented 1 year ago

will close https://github.com/CommonWealthRobotics/BowlerStudio/issues/180

madhephaestus commented 1 year ago

close CommonWealthRobotics/BowlerStudio#145

madhephaestus commented 1 year ago

close https://github.com/CommonWealthRobotics/BowlerStudio/issues/184

JansenSmith commented 1 year ago

i'm still using this branch in source, and i've yet to encounter an OutOfMemory exception, handled appropriately or otherwise. still looking

JansenSmith commented 1 year ago

@madhephaestus i still haven't seen a local error msg, but i AM experiencing some stun-lock instability. happens ~twice per day. is this related to the change?

JansenSmith commented 1 year ago

btw, i think we would RATHER just keep reporting the issue (so at least we know this keeps happening to folks) if the alternative is a stun-locked Bowler with no "You have run out of RAM. You must construct additional pylons."