0000639: Exception when exiting from a rendering because of haltspp

View Issue Details [ Jump to Notes ]

[ Issue History ] [ Print ]

Project

Category

View Status

Date Submitted

Last Update

0000639

LuxRender

Core

public

2009-11-13 00:58

2009-12-22 01:49

Reporter

Dade

Assigned To

Dade

Priority

normal

Severity

major

Reproducibility

sometimes

Status

closed

Resolution

fixed

Platform

OS Version

Product Version

0.6

Target Version

Fixed in Version

0.6.1

Summary

0000639: Exception when exiting from a rendering because of haltspp

Description

It is quite uncommon but sometime Lux throws an exception on exit with haltspp enabled:

[Lux 2009-Nov-12 22:59:47 INFO : 0] [4 threads] 00:05:00 384823 samples/sec 386672 samples/totsec 496.257 samples/pix
[Lux 2009-Nov-12 22:59:52 INFO : 0] [4 threads] 00:05:05 388886 samples/sec 386708 samples/totsec 504.56 samples/pix
[Lux 2009-Nov-12 22:59:57 INFO : 0] Writing Tonemapped PNG image to file /home/david/projects/luxrender-dev/scenes/anello//default-00061.png
[Lux 2009-Nov-12 22:59:57 INFO : 0] 100% rendering done [4 threads] 00:05:10
luxconsole: /usr/include/boost/thread/pthread/mutex.hpp:50: void boost::mutex::lock(): Assertion `!pthread_mutex_lock(&m)' failed.
Aborted
Therewas an error runnig last commands (exist status: 34304)

Tags

No tags attached.

Mercurial Changeset #

Requires Documentation Update

Requires Exporter Update

Attached Files

Relationships

parent of

0000662

closed

Dade

Luxconsole wait up to 5secs before to exit

Notes
(0001745) Dade (developer) 2009-11-13 01:56	The print: [Lux 2009-Nov-12 22:59:57 INFO : 0] 100% rendering done [4 threads] 00:05:10 is interesting because it tells me that everything has already been done/terminated. There is only another Lux API call efore to exit: luxCleanup(). Otherwise the problem could be in the infoThread(), mmmm, I think it is there.

(0001746) Dade (developer) 2009-11-13 02:24	Yup, I have to stop the infoThread() before to call luxCleanup(). By removing the sleep() in infoThread() in order to increase the probability of the event I get a core dump often. It is not the "Assertion failed" but they could both have the same cause. Stopping infoThread() before to call luxCleanup() solved the problem. Going to check LuxGUI.

(0001747) Dade (developer) 2009-11-13 02:32	LuxGUI should be fine. I commited the patch.

Issue History
Date Modified	Username	Field	Change
2009-11-13 00:58	Dade	New Issue
2009-11-13 01:25	Dade	Status	new => assigned
2009-11-13 01:25	Dade	Assigned To	=> Dade
2009-11-13 01:56	Dade	Note Added: 0001745
2009-11-13 02:24	Dade	Note Added: 0001746
2009-11-13 02:30	Dade	Summary	Exception when exiting form a rendering because of haltspp => Exception when exiting from a rendering because of haltspp
2009-11-13 02:32	Dade	Note Added: 0001747
2009-11-13 02:32	Dade	Status	assigned => feedback
2009-11-18 04:21	Dade	Status	feedback => resolved
2009-11-18 04:21	Dade	Fixed in Version	=> 0.6.1
2009-11-18 04:21	Dade	Resolution	open => fixed
2009-11-27 00:29	Dade	Relationship added	parent of 0000662
2009-12-22 01:49	jeanphi	Status	resolved => closed