there's some background on the cuda 9.1/10 issue in T56858 but as i said earlier if 9.1 doesn't work for this issue, it's very likely a different issue and we shouldn't be mixing the reports cause that'll just confuse everyone.

with that function name change lgtm.

please do not assign priority your self, since it actually makes it less likely for the people triaging the bug tracker to look at your report.

GT555M is an sm_21 card, for which support in cuda has been dropped.

On windows all dialogs have the button order by design agree/disagree/cancel , this is what people expect, this is what every other application does, this is what D3118 does, this commit doesn't do that and breaks the platform UI standards.

this wasn't enabled yet on all platforms due to wrong order of the buttons on some playforms (*cough*windows*cough*) and lack of a 'default' button support, see D3118 for details, please revert for the time being.

if 9.1 doesn't work, it's definitely a different bug, opening back up.

It's a bug in cuda10(some cards)/9.2(all cards) we cannot work around, nvidia has been informed, there's nothing we can do on our side, so no need to keep a ticket open.

also that's a cuda 10 bug, use 9.1 and you'll be allright.

please do not assign priority your self.

Which is one of the reasons i picked sentry unlike other solutions in this space, it's opensource and you can run it on your own servers.

We got a native crackle a while ago, grab a nightly build at http://builder.blender.org and enjoy.

you can leave out the url bit, by just mentioning D3971 in the text, phabricator will link the two for you :)

you can also convince wget to ignore robots.txt with -e robots=off

Someone installed cuda 9.2 on the buildbot.. which is known bad.

This broke atleast the windows x86 build (even with embree disabled) i'm not sure we have a macro for conditional X86 padding only, so i'll leave this for @Brecht Van Lommel (brecht) and @Stefan Werner (swerner) to fix.

did some googling, this seems to be the same issue, but yikes, looks messy.

@Brecht Van Lommel (brecht) wants to add some feature to D3118 which could be a bit, so we still might have to look into fixing this ;/

you can pass MB_TOPMOST to the messagebox function and it'll be topmost, however i'd prefer we'd land D3118 which gets rid of the OS specific messagebox all together

That may well be, but i'm not gonna change a legal text on my own without explicit instructions to do so.

I can change it into whatever, but i'm gonna need some guidance from @Ton Roosendaal (ton) what he wants

for future reference, when you drag in an attachment make sure the { and } have a space around it changing your comment from

This is a general support issue and not a software error we can investigate.

This is a general support issue and not a software error we can investigate.

If you drop in an software opengl implementation, things are gonna be slow, If blender doesn't run without it you either have an old video card, or have driver issues.

Thanks for the report, but this add-on is not developed by Blender, please report the bug to the original author.

• Fix comment style.

I transferred the quick start here but it took me longer to port it to mediawiki than to write the original and it looks rather terrible. even basic things like note don't work on our wiki, It's unpleasant for the end user to read, and frustrating for the dev to write. Unless forced i'm unlikely to repeat this experiment.

I have a quick start guide on how to use this feature here

arc decided to make a new one instead of updating this one, i'm done fighting arc..

your card supports it, but the drivers are causing a stink, it looks like gpu-z is a little better at not crashing and burning when it encounters that, you could give nvidia support a try, but they'll probably tell you to go reinstall your computer.

That is with the dlls removed?

do tools like gpu-z also crash?

now that the bad dll's are gone, try re-installing the gpu driver (which should place fresh copies of those dlls back) and see if the problem re-appears.

If you save the file after step 11, close blender and load it up again and do step 12, does it still crash?

Why so angry? you're not listening.

yes, you messed about for 2 minutes, which is a terrible way of reproducing a bug, we need concrete steps to reproduce a bug, not a minutes long video.

can't reproduce, anyway you can shorten the reproduction from 'do random stuff for nearly 2 minutes' to

While i can't seem to reproduce the original problem of files not being re-generated , I do see value in having the glsl available in the IDE.

Thank you for the report. Currently we are aware of many issues in 2.8 and actively working to fix them. But since replying to reports takes time, we have decided to limit bug reports to crashing bugs only at this point in time.

Please don't re-open tickets, especially if they are not yours to begin with.

Is this a build from builder.blender.org or did you build it your self? if it's a homebrew build, what version of cuda did you use?

I'll leave it up to @Brecht Van Lommel (brecht) to decide if we want this in but if it does make it in, couple of things:

Give it is based on 2.8, may i recommend uploading the diff with arc?

In D3519#86370, @Stephen Swaney (stiv) wrote:

In D3519#83597, @Aaron Carlisle (Blendify) wrote:

Another option is to make this addon a part of the regular Blender distribution which would make the library available without any additional steps.

From the bug report page

Score! thanks for the quick test!

we have recently updated osl/llvm, is this still an issue? @Tim (ptim) can you check with a nightly build?

• remove last bits of breakpad

Forgot one update, the build in crash moved to the debug menu, value of 1 now crashes blender (this will need to go before landing, but it's easy to have to test)

• Updated with feedback.

No idea, if you run the installer again, it should give you a repair/uninstall option, does uninstall work from there?

from the bug report page

Can confirm in master on windows.

blender is currently building on centos, while there are no binaries available , two users have made available a docker for building blender, available in this thread

the sound message is just a warning, and is unrelated to your actual issue of blender not starting.

• Updated with feedback.

In D3706#85336, @Brecht Van Lommel (brecht) wrote:

I don't immediately have good ideas for how to avoid such crashes. I guess you would have to do a bit like the kernel, compile the AVX tests in a separate file with different compile flags, but not sure how easy that is with gtest.