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 591031 - reading ISOs twice for checksumming and burning is slow
reading ISOs twice for checksumming and burning is slow
Status: RESOLVED OBSOLETE
Product: brasero
Classification: Applications
Component: general
2.26.1
Other All
: Normal minor
: ---
Assigned To: Brasero maintainer(s)
Brasero maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2009-08-07 06:08 UTC by Greg Poirier
Modified: 2018-09-21 16:41 UTC
See Also:
GNOME target: ---
GNOME version: 2.25/2.26


Description Greg Poirier 2009-08-07 06:08:32 UTC 
The following bug was entered at https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/410085

"Recently I burned a DVD-R from an ISO image file.
It was very slow.

The reason: brasero reads the input ISO file twice, once for the checksum, then again for the actual burning.

In my case the file was heavily fragmented and the performance was very poor (5 minutes to read the file instead of 1 minute when not fragmented).

The fragmentation is a separate issue, but braseo could be optimized by reading the file only once.
While burning, it could parallelly compute the checksum.

Or if that is hard to implement: Do not use checksum at all, but compare the burned data to the input file. This way in case of verify error, the exact point(s)/sectors(s) of mismatch can be identified."

Other information:
ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 9.04
Package: brasero 2.26.1-0ubuntu1
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: brasero
Uname: Linux 2.6.28-14-generic i686
Comment 1 David Balažic 2010-10-11 00:26:28 UTC 
Same in 2.32, see ubuntu bug.
Comment 2 GNOME Infrastructure Team 2018-09-21 16:41:14 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/brasero/issues/63.