Please run Blender from a terminal and use the 'Edit Task' link to paste it in the task description. That'll give us much more info about what's going on.
Also please give us the exact link you downloaded (which will include the Git revision hash) so that we know exactly which version of Blender you tested.

Indeed we should kill all jobtypes (not just rendering) in that case.

Could you try a new build from https://builder.blender.org/download?

As mentioned in T55034, editing multiple selected items with Alt+Click is meant for properties editing, it doesnt handle operators.
Operators decide for themselves if they want to work on active or all selected (some do, some dont...)

In T55520#512761, @Philipp Oeser (lichtwerk) wrote:

Total shot in the dark, but:

• do you have any antivirus running (could you try disabling?) ?
• does it also happen with --factory-startup?
  
  Marking as incomplete until we have an answer on these two questions...

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 module team members.

Yes sounds like a to-do, I just don't want this to get lost.

Ah, that works. There's a different issue (multi-selection of objects, and 'add to group'). I'll file a separate ticket for this - I guess it's not related to this specific case.

The issue is that the operatots have option to set the mask weight for example. This should work similar to the lasso mask feature.

The issue is that the operatots have option to set the mask weight for example. This should work similar to the lasso mask feature.

crashes in write_workspace().
Not exactly sure what changed there recently, but 2.8 is still unstable in certain areas (and absolutely not recommended to do production in)

Doesnt seem to be an issue with the new dependency graph.
[run blender with --enable-new-depsgraph option]

Does not work on 2.8 ed428b2 either.

Total shot in the dark, but:

Closing, many border operations don't have redo support.

reg. Fill Mask: operator has OPTYPE_REGISTER but no OPTYPE_UNDO (undo comes from own "internal sculpt" undo push here ).
OPTYPE_UNDO could be added, but we would run into the "double-undo-push" issue mentioned in T55399

Note that it is still a little early to report bugs for 2.8 due to following policy:

Yes, this is supposed to be working (and it does for me)
Checked my local master build and todays buildbot build (linux).
Created 3 empties, added Suzanne, Ctr+G, selected all three empties, Alt+click Group type in object duplication, Alt+Click on group selector and choose "Group" --> works here.

Some things you could try:

Looks like this is not standard behavior (and this might be caused by an addon or modified keybindings?)

Could you upload an example that fails here?
(just drag and drop an .obj or .3ds into the comment and I'll have a look)

Not many people will experience this bug. Maybe automaticly disabling avx2 in this case?

I've done my best to create a log of this happening, for some reaon I'm not seeing the python traceback when it crashes any more, but it happens reliably every time. If anyone can point me to some documentation on how to get a more verbose log, I'm happy to oblige.

@Lukas Stockner (lukasstockner97) , @Brecht Van Lommel (brecht) feels like a codegen bug, in a compiler we're soon gonna drop anyhow, not sure if it's worth spending time tracking it down.

I tried the vc14 version and it works. So this bug seems to be only happening when using Avx2, Windows and the old compiler. Very exclusive little bug. :-)

I can only seem to reproduce this with msvc2013 and avx2, @Falk Müller (xharthok) can you try a build from the bot marked with 'New Compiler' (has vc14 in the filename) and see if it works for you without having disable avx2?

In T54968#512092, @Philipp Oeser (lichtwerk) wrote:

@Frank (Ottovan) : sorry I couldnt help further, but may I ask why this is resolved/invalid for you now?
[if there is something you've done to make it work, please let us know -- as others might benefit from your findings as well...]

Thanks for the tip! I disabled AVX2 and everything renders fine.

same issue for me on arch linux and ubuntu 18.04
maybe a too old graphic card ? ATI Radeon HD 5750....

Is this supposed to be resolved in the 2.79 code? I'm still seeing this behavior in the current nightly builds, so wanted to check

Thank you Philipp :)

Confirmed by @LazyDodo (LazyDodo), only seems to happen on AVX2-capable processors on Windows.