Bug #857
closedCrash on hiding column in WTableView
0%
Description
Crash on workstation with 512 mb of ram when hiding column in recreated WTableView. Possibly due to uninitialized firstColumn_ and lastColumn_ members in WTableView as initializing them solved the problem.
Crash was in WTableView::updateColumnOffsets() method on line "w->setOffsets(totalRendered, Left);" as "w" was NULL.
Updated by Koen Deforche almost 13 years ago
- Status changed from New to Resolved
- Assignee set to Koen Deforche
Hey,
With recreated, I assume you mean setModel() or a anything that causes a model reset signal ?
If so, I think I've found the culprit.
Regards,
koen
Updated by dima s almost 13 years ago
Hello,
Koen Deforche wrote:
With recreated, I assume you mean setModel() or a anything that causes a model reset signal ?
No. I mean that I destroy WTableView (using clear() for the container containing it) and create new WTableView, but as I see in debugger memory for the newly created WTableView is assigned from the same region as for previous WTableView and lastColumn_ member gets value from the previous WTableView which was destroyed. Thus I get crash when I call hideColumn() for the newly created WTableView. This issue appears on the wirtual machine with 512 mb or ram and doesn't on my phisical host with 2 gb or ram.
Regards,
dima
Updated by Koen Deforche almost 13 years ago
Hey,
I notice a fix w.r.t. initialization of firstColumn_ and lastColumn_ in git of April 12th.
Does this problem still occur with a git version of Wt ?
Regards,
koen
Updated by Koen Deforche almost 13 years ago
- Status changed from Resolved to Closed
Updated by dima s almost 13 years ago
Hi,
No, problem doesn't occur with git version of Wt.
Regards,
dima