Skip to content

Windows build: createdb.js fails with ERRORLEVEL 3 #62

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

Closed
cmundi opened this issue Feb 13, 2012 · 4 comments
Closed

Windows build: createdb.js fails with ERRORLEVEL 3 #62

cmundi opened this issue Feb 13, 2012 · 4 comments

Comments

@cmundi
Copy link

cmundi commented Feb 13, 2012

I built node-sqlite3 (in Release) for Windows using the work of TooTallNate here: #61 and verified that the small Ipsum Lorem example in the README.md worked as expected, using node 0.6.10.

Then I tried to node createdb.js. After the usual spike in memory use, I ended up with a big.db of zero bytes and "DOS" ERRORLEVEL equal to 3.

If I reduce the number of rows inserted by createdb.js from 10 million to 1 million, I get a database of size consistent with expectations (about 65MB) for the random strings.

Platform is 32-bit Windows XP.

My typical uses of sqlite are for small test databases, so I have no idea if this is an issue with SQLite on Windows (I know for a fact that this problem does not occur on 64-bit Linux where I have build and tested node-sqlite3 with node0.6.10.) or node or node-sqlite on Windows.

Please let me know how I can provide a more useful report.

@cmundi
Copy link
Author

cmundi commented Feb 13, 2012

Forgot to mention... this box has 2GB of RAM and plenty of swap space

@cmundi
Copy link
Author

cmundi commented Feb 13, 2012

I have verified the same behavior on a second 32-bit Windows XP box.

node .\test\support\createdb.js ==> abnormal termination, zero-size for big.db

The pagefile grows to about 2.4GB (from a quiescent state of ~500MB) and then node dies.

@cmundi
Copy link
Author

cmundi commented Feb 13, 2012

I wonder if the problem has something to do with transaction buffering on on Windows. I probably will not have time to test this week...

@springmeyer
Copy link
Contributor

we've reduced the size of the db now, so this should be avoided.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants