Bug 414343 - Getting "terminate called after throwing an instance of 'std::bad_alloc'"
Summary: Getting "terminate called after throwing an instance of 'std::bad_alloc'"
Status: RESOLVED WORKSFORME
Alias: None
Product: frameworks-threadweaver
Classification: Frameworks and Libraries
Component: general (other bugs)
Version First Reported In: 5.64.0
Platform: Microsoft Windows Microsoft Windows
: NOR crash
Target Milestone: ---
Assignee: Mirko Boehm
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-11-20 21:35 UTC by Shujaat
Modified: 2022-12-31 05:24 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Shujaat 2019-11-20 21:35:53 UTC
SUMMARY

I downloaded ThreadWeaver using "git clone git://anongit.kde.org/threadweaver.git" and built it. HellowInternet, HelloWorld and HellowWorldRaw ran fine. ThumbNailer ran fine in cases when I loaded few images but when I was loading 631 images the program crashed after loading some images. I tried for few more times and I noticed that sometimes the GUI gets hidden like being crashed but the process run in the background infinitely. In some crashes I get errors like this:

ThumbNailer.exe ...
terminate called after throwing an instance of 'std::bad_alloc'
  what():  std::bad_alloc
QObject::~QObject: Timers cannot be stopped from another thread
Uncaught exception in Job 270f89c0, aborting.01:57:56: ThumbNailer.exe exited with code 3


STEPS TO REPRODUCE
1. Run ThumbNailer 
2. Goto File-Select Files
3. Find a folder containing 631(in my case) or above images
4. Press Ctrl+A to select all images and then click Open
5. The images will start loading but soon the program will crash

OBSERVED RESULT
The ThumNailer crashes which may be due to some bugs in the ThreadWeaver.


EXPECTED RESULT
The ThumbNailer should have displayed all images in smooth manner with responsive GUI without hanging or crashing.


SOFTWARE/OS VERSIONS
Windows: 10
Qt Version: 5.12.1

ADDITIONAL INFORMATION
Comment 1 Shujaat 2019-11-20 22:52:19 UTC
getting this error too:

terminate called after throwing an instance of 'std::bad_alloc'
  what():  std::bad_alloc
QMutex: destroying locked mutex
QObject::~QObject: Timers cannot be stopped from another thread
Uncaught exception in Job 1b3682e8, aborting.03:48:17
Comment 2 Justin Zobel 2022-12-01 05:22:05 UTC
Thank you for reporting this issue in KDE software. As it was reported on an older version, can we please ask you to see if you can reproduce the issue with a more recent software version?  
  
If you can confirm this issue still exists in a recent version, please change the version field and the status to "REPORTED" when replying. Thank you!
Comment 3 Bug Janitor Service 2022-12-16 05:14:37 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Bug Janitor Service 2022-12-31 05:24:43 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!