View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0017646 | Scribus | Internal | public | 2025-10-10 08:50 | 2025-10-10 22:43 |
Reporter | tropion | Assigned To | jghali | ||
Priority | normal | Severity | minor | Reproducibility | have not tried |
Status | resolved | Resolution | fixed | ||
Product Version | 1.7.1.svn | ||||
Fixed in Version | 1.7.1.svn | ||||
Summary | 0017646: Some objects created by ColorPicker have no parent QObject | ||||
Description | The ColorPicker should have a destructor. Something like this: ColorPicker::~ColorPicker() { delete m_colorButton; delete buttonGroup; delete comboOverprint; delete checkboxUsedColors; delete contextMenu; } | ||||
Tags | No tags attached. | ||||
Patch | No | ||||
|
Practically there is no leak here either as ColorPicker is created only once during the lifetime of the application and any memory allocated by it will be freed by the system when application is closed. But some objects should be created with a parent in order to be handled by Qt QObject system. |
Date Modified | Username | Field | Change |
---|---|---|---|
2025-10-10 08:50 | tropion | New Issue | |
2025-10-10 21:35 | jghali | Note Added: 0053057 | |
2025-10-10 22:43 | jghali | Category | General => Internal |
2025-10-10 22:43 | jghali | Summary | Memory leaks => Some objects created by ColorPicker have no parent QObject |
2025-10-10 22:43 | jghali | Assigned To | => jghali |
2025-10-10 22:43 | jghali | Status | new => resolved |
2025-10-10 22:43 | jghali | Resolution | open => fixed |
2025-10-10 22:43 | jghali | Fixed in Version | => 1.7.1.svn |