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

Illegal memory access inside of SimulationMap constructor #38

Open
kolayne opened this issue Nov 19, 2020 · 1 comment · May be fixed by #58
Open

Illegal memory access inside of SimulationMap constructor #38

kolayne opened this issue Nov 19, 2020 · 1 comment · May be fixed by #58
Labels
bug Something isn't working

Comments

@kolayne
Copy link
Member

kolayne commented Nov 19, 2020

(This may be a duplicate of #29 or a symptom of #32. This is likely to be a duplicate of #31)

For smaller cubes, which seems to be not affected by #32 (at least, I'm not receiving SIGABRTs for them), another error occurs.

The app compiled for GPU fails to finish constructing a SimulationMap object because of an illegal memory access (attaching a patch I'm using to determine this)
gpu.patch.txt (GitHub doesn't allow uploading .patch files for some reason...)

The app compiled for CPU does finish SimulationMap initialization (at least for me) but fails on the second iteration of the loop:

while(true)
{
for(RunIterationFunc f : iteration_runners)
{
f(simulation_map, &iteration_number);
}
if(!send_particles_to_visualization(visualization_endpoint, simulation_map->nodes,
simulation_map->get_n_of_nodes()))
{
std::cerr << "Error sending http request to visualization. Stopping the simulation process\n";
break;
}
}

Though I'm not 100% sure it's the same issue as the problem described above...

@kolayne
Copy link
Member Author

kolayne commented Nov 19, 2020

No, this doesn't seem to be a symptom of #32, because I can reproduce the same issue in #40, which should fix #32

@kolayne kolayne added the bug Something isn't working label Nov 19, 2020
kolayne added a commit that referenced this issue Nov 24, 2021
…nstead of previous approach.

This might have fixed one or many of: #29, #31, #38

Co-authored-by: Nikolay Nechaev <Nikolay_Nechaev@mail.ru>
@kolayne kolayne linked a pull request Nov 24, 2021 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant