Free cookie consent management tool by TermsFeed Policy Generator

Opened 7 years ago

Closed 7 years ago

#2788 closed defect (done)

Blue screen on some Windows 10 systems

Reported by: gkronber Owned by: pfleck
Priority: medium Milestone: HeuristicLab 3.3.15
Component: General Version: 3.3.14
Keywords: Cc:


Change History (10)

comment:1 Changed 7 years ago by 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.

comment:2 Changed 7 years ago by jkarder

  • Owner set to architects
  • Status changed from new to assigned

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

A maximum of 25 should work.

comment:3 follow-up: Changed 7 years ago by mkommend

comment:4 in reply to: ↑ 3 Changed 7 years ago by 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.

comment:5 Changed 7 years ago by 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.

comment:6 Changed 7 years ago by pfleck


  • 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.

comment:7 Changed 7 years ago by pfleck

  • Owner changed from architects to bburlacu
  • Status changed from assigned to reviewing

comment:8 Changed 7 years ago by pfleck

  • Owner changed from bburlacu to abeham

comment:9 Changed 7 years ago by abeham

  • Owner changed from abeham to pfleck
  • Status changed from reviewing to readytorelease


comment:10 Changed 7 years ago by pfleck

  • Resolution set to done
  • Status changed from readytorelease to closed

r15038: merged r14995 r15003 from trunk to stable

Note: See TracTickets for help on using tickets.