Open rconstanzo opened 1 year ago
Got a second crash (also with a really long @hiddenlayers
network.
Also, narrowed down when it happens. It seems like I got the crash when I pause the training (i.e. toggle off the toggle in the loop) then toggle it back on. I got the instacrash when toggling it back on.
few observations:
on my machine, there is no memory leak after running it for 15 minutes without a crash - I thought of checking this since both crashes are linked to memory allocation... and I start and stop it, to no avail.
so that brings us to how we can help you help us help you: are you set up for compilation? if so you could gain 2 things:
this comes at the expense of having to compile, but also maybe being confused by which version you are actually using. I have scripts to swap them in the OS, but that might not be exciting for you. in all cases, I'm happy to help.
anyway, as I am unable to reproduce, we are stalled. let us know if you find something more reproducible.
now running for 45 minutes in 'test' compile mode, starting and stopping and resetting - still no crash.
I'll see if I can get it to crash again.
Not saying the network is useful, I was just testing different structures on to see what type/direction/style was better (maybe changing structures often, via the attrui
is a component of this?).
It could just be coincidence, but happening twice with the same object/process seems unlikely.
If you don't mind, try this version of the object (keep the other one you have for real-life use) so if it crashes we'll know better if it is fluid.verse-related and where from... fluid.libmanipulation.mxo.zip
@rconstanzo any more crash with my magic custom compile?
Was in the UK teaching, will give it a test now. Not gotten any new crashes since though (but haven't been testing super long network structures since.
As mentioned on the discourse thread got an (unrepeated) crash when trying to
fit
some data withfluid.mlpclassifier
.Attaching the isolated patch bit in question, along with the data/labels I was using at the time. Also the crash report.
This is, I believe, the crash-y bit:
crashbits.zip