After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 357433 - GIMP 2.2.11 Script-Fu Render Line Nova crashes WinXP
GIMP 2.2.11 Script-Fu Render Line Nova crashes WinXP
Status: RESOLVED FIXED
Product: GIMP
Classification: Other
Component: Script-Fu
2.2.x
Other All
: Normal critical
: ---
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2006-09-24 10:49 UTC by Eidako
Modified: 2008-01-15 13:12 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Eidako 2006-09-24 10:49:52 UTC 
Steps to reproduce:
1. (From an empty 190x100 RGB image) Script-Fu > Render > Line Nova
2. Set "randomness" to 0. Other values don't seem to matter, but tested with "Number of lines" to 72, "Sharpness" to 5, and "Offset" to 10.
3. Press "OK"

Stack trace:
(not available; sorry)

Other information:
The above operation runs for about 50-80 iterations, then abruptly stops and causes major system instability on a 2.93Ghz 248MB RAM WinXP SP2 box. CPU usage appears to stay under 20%, but Task Manager takes a long time to appear and refuses to kill both Script-Fu and GIMP; a reboot is required to return to normal.
Comment 1 weskaggs 2006-09-24 15:50:54 UTC 
Setting the randomness to 0 is a bad thing, because it shows up in the script in the following lines:

      (let ((dir0 (deg->rad direction))
	    (off (+ offset (- (modulo (rand) variation) variation/2))))

The "variation" variable is the same as the "randomness" arg.  I'm not sure what happens if you modulo by 0, but it can't be good.  Presumably the solution is to set the minimum value to 1 instead of 0.

Fixed in both branches:

2006-09-24  Bill Skaggs  <weskaggs@primate.ucdavis.edu>

	* plug-ins/script-fu/scripts/line-nova.scm: Change min for randomness
	from 0 to 1, should fix bug #357433.

If there is something wrong with this fix, please comment or reopen.