Max Frei

Thanks for the advice. I tried debugging using `cuda-gdb` but it wouldn't attach to the python process. I then started the script from the regular `gdb`, but the results seem...

I narrowed down the error a little further, and it occurs inside the `step()` function of the Adam optimizer. Since (apart from some BSDF parameters), I'm also optimizing a texture,...

I already figured that I should write more about my setup: I use an envmap and two principled BSDFs, all of which are optimized using Adam. Integrator is PRB. The...

@merlinND Thanks for the hint! I tried to add a `dr.sync_thread()` before and after the Mitsuba generator update (not yet before and after the PyTorch discriminator update). Unfortunately, it still...

I did some more testing and found that older versions of `mitsuba` (and therefore `drjit`) work for me. To find the exact commit that causes the error, I'm currently doing...

Thanks for the hints! > I don't think explicit synchronization is ever need now I tried explicit synchronization at different parts of my code, but it didn't help, which is...

Over the weekend, I made progress on the bisection. While I initially thought that the error was pre-3.1, that was actually a different error, which has been fixed by now....

> I also think the commit you pointed out simply altered the symptom. That would mean that the error was introduced in this range: ``` ------------- Critical Dr.Jit compiler failure:...

> Based on my currently running bisection run, I even feel fairly confident to say that the error is related to [90f0d733](https://github.com/mitsuba-renderer/mitsuba3/commit/90f0d733822c480ea5403d5941ba747058bcd45b). What I intended to say was that I'm...

Interestingly enough, I just finished the test run of [16b133ec](https://github.com/mitsuba-renderer/mitsuba3/commit/16b133ecb940346ce17959589e0ce567eb7181e5), and it crashed on the very last iteration: ``` Critical Dr.Jit compiler failure: jit_assemble(): schedule contains variable r396505013 with incompatible...