Bug 297747 - Resizing an artistic text height to zero can cause a crash
Summary: Resizing an artistic text height to zero can cause a crash
Status: RESOLVED DUPLICATE of bug 299580
Alias: None
Product: calligracommon
Classification: Applications
Component: flake-plugins (show other bugs)
Version: 2.4-snapshots
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Calligra Bugs
URL:
Keywords:
: 297454 (view as bug list)
Depends on:
Blocks:
 
Reported: 2012-04-09 00:00 UTC by Antoine
Modified: 2012-05-08 06:51 UTC (History)
3 users (show)

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

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Antoine 2012-04-09 00:00:49 UTC 
Create an artistic text.
Set its height to zero with the handle on the bottom edge.
Crash.
I can reproduce easily in Krita, Words, flow and Karbon.
In calligraflow: it doesn't crash; the shape is stuck, with x,y,w and h set to precisely 138.89 inches.
Comment 1 Halla Rempt 2012-04-09 11:37:55 UTC 
*** Bug 297454 has been marked as a duplicate of this bug. ***
Comment 2 T Zachmann 2012-04-18 09:41:26 UTC 
It happens for me after some time after setting the with/height to 0 in the docker. And then hiding and showing the screen.

With valgrind I get the following error messages before the crash

==31728== Warning: set address range perms: large range [0x453d0030, 0x553d0050) (noaccess)
==31728== Warning: set address range perms: large range [0x953d2040, 0xb53d2040) (undefined)
==31728== Warning: set address range perms: large range [0x553d1030, 0x753d1050) (noaccess)
==31728== Warning: silly arg (-2147483648) to realloc()
==31728== Warning: set address range perms: large range [0x753d2030, 0xb53d2050) (noaccess)

and after that it seems the memory is corrupted.
Comment 3 Halla Rempt 2012-05-08 06:51:33 UTC 
Same bug as 299580 -- that report has a backtrace.

*** This bug has been marked as a duplicate of bug 299580 ***