Skip to content
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

Adding hundreds of millions of clauses crashes solve #27

Closed
nmz787 opened this issue Jun 30, 2016 · 2 comments
Closed

Adding hundreds of millions of clauses crashes solve #27

nmz787 opened this issue Jun 30, 2016 · 2 comments
Labels
locked [bot] locked due to inactivity stale::closed [bot] closed after being marked as stale stale [bot] marked as stale due to inactivity

Comments

@nmz787
Copy link

nmz787 commented Jun 30, 2016

I assumed this had something to do with passing too-large an array to the solve method at once... so I attempted to enhance the extension with a Solver class (I didn't change it's name from the Noddy template example though):
master...nmz787:patch-1

but when I run this, at 234 million clauses the python.exe RAM usage is just under 4GB (~3.89 GB), and it crashes.

I am not sure what to do, but will keep thinking.

@nmz787
Copy link
Author

nmz787 commented Jun 30, 2016

This will also crash pycosat as-is, without my modifications:
pycosat.solve([[i for i in range(1,235000000)]])

confirmed by a friend who initially tried this on his pypi installed pycosat:
pycosat.solve([[i for i in range(1,1000000000)]])

@github-actions
Copy link

Hi there, thank you for your contribution!

This issue has been automatically marked as stale because it has not had recent activity. It will be closed automatically if no further activity occurs.

If you would like this issue to remain open please:

  1. Verify that you can still reproduce the issue at hand
  2. Comment that the issue is still reproducible and include:
    - What OS and version you reproduced the issue on
    - What steps you followed to reproduce the issue

NOTE: If this issue was closed prematurely, please leave a comment.

Thanks!

@github-actions github-actions bot added the stale [bot] marked as stale due to inactivity label Mar 15, 2022
@github-actions github-actions bot added the stale::closed [bot] closed after being marked as stale label May 14, 2022
@github-actions github-actions bot added the locked [bot] locked due to inactivity label May 14, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 14, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
locked [bot] locked due to inactivity stale::closed [bot] closed after being marked as stale stale [bot] marked as stale due to inactivity
Projects
Archived in project
Development

No branches or pull requests

1 participant