Blue screen on some Windows 10 systems

[mkommend]

I suspect this is the old, well-known bug with too many nested controls in winforms apps(​stackoverflow, ​microsoft support).

A possible way to avoid the BSOD is that make the maximum nesting level of controls configurable in the app.config. A draw back of setting a smaller number is that the user experience suffers.

[jkarder]

r14995: added new setting for the maximum number of nested controls

A maximum of 25 should work.

[mkommend]

​Detect .Net versions

[pfleck]

Replying to mkommend:

​Detect .Net versions

I checked the release numbers as the link describes on my notebook (creators update) and workstation (no creators update). Works for me.

[pfleck]

I did a few tests with the nesting level.

• With a max nesting level of ~30, BSODs regularly occurred.
• With a max nesting level of ~25, I never had a BSOD.

For DataAnalysis (SymReg in an OSGA), a nesting level of 27 worked fine for me, however; a nesting level of 28 caused BSODs.

Then, I wrote a small application that iteratively increases nesting and prints the current nesting level. Nesting levels of 33 caused a BSOD, thus I assume that there is a maximum nesting level for WinForms of 32.

Because we only check the nesting level for the ItemViews and each view usually has some nesting levels itself, I suggest we use <= 27 as a maximum nesting level. In this case we have 5 nesting levels available for the content of each ItemView. ItemViews with more internal nesting levels could still cause a BSOD.

[pfleck]

r15003

• Added a dialog for changing the maximum nesting level (Views menu item).
• For systems that have the creators update installed and a high nesting level, a warning will be displayed with the option to lower the maximum nesting level.

[abeham]

Ok

[pfleck]

r15038: merged r14995 r15003 from trunk to stable