You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At this point, by looking at the ReadMe and the Issues of these project it's quite obvious that there are a lot of people having trouble exporting the models (myself included). However the reason for this seems to be varied, sometimes it's because a flag on the webui as the Readme describes:
-`medvram` and `lowvram` Have caused issues when compiling the engine.
Sometimes this only works on some forks of webui #262 (comment)
I am willing to bet this sometimes this does not work depending on some other plugin that does something that just messes with this.
Also sometimes the process crashes on a cuda out of memory as seen #175
I think it's quite clearly that if the exporting process had a Command Line Interface that could be called so only the exporting process would running without interference, then (hopefully) most of this problems should disappear.
Also in terms of bug reports, people could report issues describing what happen when the CLI is failing, which would only involve the TensorRT process (hopefully) reducing the complexity of solving bugs.
The text was updated successfully, but these errors were encountered:
At this point, by looking at the ReadMe and the Issues of these project it's quite obvious that there are a lot of people having trouble exporting the models (myself included). However the reason for this seems to be varied, sometimes it's because a flag on the webui as the Readme describes:
Stable-Diffusion-WebUI-TensorRT/README.md
Line 52 in b75f560
Sometimes this only works on some forks of webui #262 (comment)
I am willing to bet this sometimes this does not work depending on some other plugin that does something that just messes with this.
Also sometimes the process crashes on a
cuda out of memory
as seen #175I think it's quite clearly that if the exporting process had a Command Line Interface that could be called so only the exporting process would running without interference, then (hopefully) most of this problems should disappear.
Also in terms of bug reports, people could report issues describing what happen when the CLI is failing, which would only involve the TensorRT process (hopefully) reducing the complexity of solving bugs.
The text was updated successfully, but these errors were encountered: