Solving issue 2023: "Pseudo memory leak with Detail window + memory handling optimization"
The Detail window buffers are now freed up when the it is closed. The CIECAM buffers are allocated only if necessary now, and if the single block allocation fails, it will try to allocate it in several blocks.
This commit is contained in:
@@ -82,15 +82,15 @@ void ImageArea::on_resized (Gtk::Allocation& req) {
|
||||
mainCropWindow->addCropWindowListener (this);
|
||||
mainCropWindow->setCropGUIListener (cropgl);
|
||||
mainCropWindow->setPointerMotionListener (pmlistener);
|
||||
mainCropWindow->setPointerMotionHListener (pmhlistener);
|
||||
mainCropWindow->setPointerMotionHListener (pmhlistener);
|
||||
mainCropWindow->setPosition (0, 0);
|
||||
mainCropWindow->setSize (get_width(), get_height(), false); // this execute the refresh itself
|
||||
}
|
||||
else {
|
||||
mainCropWindow->setSize (get_width(), get_height());
|
||||
}
|
||||
parent->syncBeforeAfterViews();
|
||||
}
|
||||
parent->syncBeforeAfterViews();
|
||||
}
|
||||
}
|
||||
|
||||
void ImageArea::setImProcCoordinator (rtengine::StagedImageProcessor* ipc_) {
|
||||
|
Reference in New Issue
Block a user