Please follow our submission template and guidelines and make a complete, valid bug report, with required info, precise description of the issue, precise steps to reproduce it, small and simple .blend and/or other files to do so if needed, etc.

Please dont set priority yourself, someone will do that for you.
In my case, I'm not getting a crash with your file (fedora27, 970m with 390.59 drivers), but maybe someone else can reproduce?

Can confirm. But only if you use the Pipette icon button from the popover.
Works as expected if you use Search in the 3D view and invoke "Sample Detail size" from there...

@Bastien Montagne (mont29) fixed in rB579631819f0136ab0fbb0f6c7c21265b468940dc

note atm. only crashes in 2.8 are accepted in the tracker, but had a quick glimpse and D3542 fixes the operator (not the viewport drawing)

• Do you get any error messages?
• Do you see new object(s) in the Outliner?
• Most important: Could you share an .obj that fails for you? (just drag and drop into a comment here)

ah, I see, committed rBA66fe0a63528b

see also T45991.
Finding the logic of "reverse_transfer" a bit confusing here:

• tooltip is confusing then ["from active to selected" is wrong... I know it's a generic operator but still...]
• we cant select a source group (its reversed now -- for the generic operator you cant select a destination group since we may transfer to several objects at once, which makes sense, but...)
• looks like the enums are also mixed up ( By Name [DT_LAYERS_NAME_DST] will act as All Layers [DT_LAYERS_ALL_SRC], choosing By Order wont have an effect cause there is no equivalent in the 'reversed' enum... )

committed a fix for the issue reported. Regarding the other change in the diff: @Kesk Y (icyp) : could you open another report for this?

Cannot confirm here (fedora27, 970m, 390.59 drivers)

Marking as incomplete until we have an example .blend

see commit rB8c957468bcd5

@Campbell Barton (campbellbarton) commited rB8c957468bcd5

note this is against 2.8, not sure if this should be in 2.79 as well?

While not exactly a bug, D3536 should do it?

requested changes by @Brecht Van Lommel (brecht)

Not sure I can follow:

• How are you actually setting a value of zero for Frames (curve.path_duration)? This should be clamped to 1?
• This should be set to 100 Frames by default?
• at a value of one for Frames (which should be the minimum), or above one, the system should behave as expected? Also see the manual

Confirmed, often we dont have a first TreeElement in SpaceOops->tree then.

Confirmed, caused by rBddee0931b8687d01186f1941d483c6b3622d1833

Can confirm this, it is the curve objects causing this.
Just adding a curve in an empty scene causes the same crash...

commited with less (10) cache frames in tests
rBAST4e1c2d1bbb72da1fc48134fb3bc46af75aec34fb

add unittests
use dict lookup for cache extension

Cannot reproduce (rB405c6c077f6e4a8c9760afef693219859d6df3ba, fedora 27, 970m, 390.59 driver)

Thanx for reporting back, and glad it is solved!

fixed by rB7d355008bfeb

You can create a differential here: https://developer.blender.org/differential/diff/create/

fix in D3518

If I understand correctly, this issue is now solved?
Regarding rendering speed: there are probably ways to achieve this (reducing geometry resolution, sampling strategies, ...), but this is more of a general support issue and not a software error we can investigate.

Cannot reproduce (rB405c6c077f6e4a8c9760afef693219859d6df3ba, fedora 27, 970m, 390.59 driver)

Cannot reproduce (rB405c6c077f6e4a8c9760afef693219859d6df3ba, fedora 27, 970m, 390.59 driver)

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.

working fine here (rB268bcb802716)

Confirmed, crashes here (where TransDataNla tdn is NULL)

1  recalcData_nla           transform_generics.c 479  0x1aebbb9 
2  recalcData               transform_generics.c 1092 0x1aeda17 
3  applyTranslation         transform.c          4569 0x1aa3bf3 
4  transformApply           transform.c          2453 0x1a9d40e 
5  transform_modal          transform_ops.c      412  0x1afbc21

@Campbell Barton (campbellbarton): Should it be like P748 (pretty much shot in the dark -- havent read relating code much...)?

Confirmed (the scale / location case), will have a look later...

Renders fine here.

Assuming we are talking about https://www.crowd-render.com/:

It's still a bit too early to report issues for 2.8, see following policy:

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.

Sorry about the regression tag, 2.79b with bmesh boolean was also bad...
So, seems to be limitation with bmesh booleans not supporting cycles motion blur in certain scenarios... (e..g. frame 462 in example file is bad, 461 is good, 463 also is...)

causes T55106

It has to do with cycles motion blur, 2.79b seems to render fine.
Disabeling motion blur or setting it to Center on Frame seems to render the boolean OK.

Please dont post the files elsewhere (you can just drag and drop them here...)
Also: link to the files on google drive is broken...
Also: if there is anything we should know from that course in order to reproduce the issue: this wont help as this is a closed course [not everyone is a CGCookie member...], so if there are additional steps to reproduce: please post them here...

This is by design (and not a bug)

Looks like a graphics driver problem. You could try the following:

Like @Konstantin (Ko) said, unfortunately, the GeForce 9600M wont suffice...

D3512 should fix the freeze.

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.

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.

Cannot confirm here.

I've uploaded the blend file if anyone wants to take a look.

This could be a graphics driver problem. Couple of things you could try:

Not sure what the status of OpenCL on Intel is, officially there is only support for AMD/NVidia cards afaik , see the manual

I'm afraid we need a bit more information here:

@Phil Stopford (philstopford) : thx for getting back, for reference: we are talking about https://devtalk.blender.org/t/origin-of-uv-map-limit-in-blender/1014, right?
Anyways, dont think this additional background info would change the fact that this is not a bug [imo].

Could confirm the crash in rB6cd0484de8c7 but this was since resolved (think in rBf8a3636374b7)