-
Notifications
You must be signed in to change notification settings - Fork 3.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Exception: 'access violation reading' while training with init_model #2249
Comments
@MaxtoqOV did you try it without dart? |
@guolinke I've just tried with the other available algorithms and the error doesn't occur. |
Also I noticed that early stopping does not work with dart. I don't know if that's normal, I didn't see anything about that in the doc. |
for early stopping, refer to #1893, I think some documents is added. |
@MaxtoqOV did you train the init_model by the dart as well? |
@guolinke Yes, as you can see in the code (despite the display bug, sorry about that), the booster is created during the first iteration of the loop. Thus the init_model has the exact same parameters than the following ones. |
indeed, I find a bug, fixes are in #2251, can you have a try? |
Thanks for the quick fix. It seems to be working well now. |
Hi, I get an 'OSError: exception: access violation reading 0x000001C0D2851338' while using lightgbm.train with an already existing Booster as 'init_model' (see code below).
The error occurs after a few training iterations. The number of iterations isn't always the same: I've had 4, 7 and 3598, and sometimes it works well... completely random.
I had never seen this error before starting using the 'init_model' feature so I assume there's a bug with it.
Environment info
Operating System: Windows 10
CPU/GPU model: Intel i7 6700HQ
C++/Python/R version: Python 3.7.1
LightGBM version or commit hash: 2.2.3
Error message
Reproducible examples
`gbm = None
for i in (0.4, 0.3, 0.2):
train_X, test_X, train_y, test_y = train_test_split(X, y, test_size=i, shuffle=False)
Steps to reproduce
see code.
The text was updated successfully, but these errors were encountered: