Ticket #11872 (Inconsistency between reported partition size value and actual partition ...) created
While trying to create a partition (after initializing partition map) when the user tries to take the offset bar to the left most extreme , then even though the partition size is zero, since the offset reported in the text box is zero, the value displayed is non-zero. Once taken to the left most extreme then even on typing the value of offset as zero the partition size value is reported incorrectly.
But if the offset is moved to somewhere else other than left most extreme , then on typing the value 0 in the offset text box the correct value gets displayed. This bug can be easily reproduced with large sized drives. In my case I had a 2TB (virtual) drive and I was trying to create a partition with 1TB space in the partition map.
Sorry to reopen, as my test was done using x86_gcc2 WebKit. The 64 bit build has not been updated to WebKit 1.4.10 yet, and is still crashing on launch. I will test it once the updated 64 bit WebKit is released.
This one has been fixed. The explanation is that PackageInfoView::SetPackage() had released the previously showing package too early. When it was the holder of the last reference, some data from the package info was still used after releasing it in its sub-views for comparing with the new content to be shown.
Fixed with hrev48825.
I'm sorry, the file seems to be called ReadMe.md (I went by the commit message instead of actually checking the tree).