Bad allocation exception

SummerZ2020 · June 23, 2020, 8:05am

Operating system:windows
Slicer version:4.11 2020-6-15
Expected behavior:The segment operation can be done successfully.
Actual behavior: bad allocation exception popped up.
I add a CT image volume which contains 2748 images. and then i use “Threshold” to segment first, and then I clicked “Islands” and choose “Remove small islands” to remove the islands which voxel number is smaller than 500. And then the exception popped up. The cpu memory occupied by Slicer app is up to almost 8 GB. see the screenshot below.

pieper · June 23, 2020, 1:08pm

That’s not really a bug, you just ran out of memory. Options are to get more memory, allocate more virtual memory, crop the volume, or choose different segmentation methods. For example, you might try a denoising filter on the images first, so you have fewer islands.

SummerZ2020 · June 24, 2020, 1:37am

I see, thanks a lot.

muratmaga · June 24, 2020, 3:02am

Is it possible to catch these bad allocation errors and display a proper out of memory error with out standard suggestion of either increasing the physical memory, virtual memory or downsample the image.
@pieper @lassoan @jcfr

pieper · June 24, 2020, 12:22pm

I was thinking the same thing - bad allocation may not be clear to non-programmers, and it is misleading in this case, since it says it’s a Slicer error, which implies bug. bad allocation is still a pretty non-specific error because it could be models or algorithms throwing the error so users will still need to come up with their own strategy to fix it. Most of the message is correct though, since we don’t know where the error occurred it’s not recoverable in general and the user should save and restart the application.

I added [an issue]. Here’s the code in case anyone wants to take a shot at it.

github.com

Slicer/Slicer/blob/dfef9574096a10c4f02337b59c5edfd6810b55db/Base/QTGUI/qSlicerApplication.cxx#L390-L417


bool qSlicerApplication::notify(QObject *receiver, QEvent *event)
{
  try
    {
    return QApplication::notify(receiver, event);
    }
  catch( std::exception& exception )
    {
    QString errorMessage;
    errorMessage = tr("%1 has caught an internal error.\n\n").arg(this->applicationName());
    errorMessage += tr("You may be able to continue from this point, but results are undefined.\n\n");
    errorMessage += tr("Suggested action is to save your work and restart.");
    errorMessage += tr("\n\nIf you have a repeatable sequence of steps that causes this message, ");
    errorMessage += tr("please report the issue following instructions available at http://slicer.org\n\n\n");
    errorMessage += tr("The message detail is:\n\n");
    errorMessage += tr("Exception thrown in event: ") + exception.what();
    qCritical() << errorMessage;
    if (this->commandOptions()->isTestingEnabled())
      {
      this->exit(EXIT_FAILURE);

This file has been truncated. show original

lassoan · June 24, 2020, 4:33pm

Good idea, I’ve added an issue to not forget about it: https://github.com/Slicer/Slicer/issues/5011

Topic		Replies	Views
Segmentation effects crashing Slicer Support	6	1816	August 2, 2019
Bad_alloc error while using margin effect in Segment editor module Support	1	442	June 10, 2020
Bad allocation errors when placing closed curves Support	12	43	September 29, 2024
Internal error : Bad array new length Support segmentation	3	897	February 13, 2020
3D slicer is keep crashing even though there is enough memory Support	8	5838	August 26, 2021

Bad allocation exception

Related topics