#15944 closed bug (fixed)
DiskUsage won't launch with many mounted volumes
Reported by: | humdinger | Owned by: | nobody |
---|---|---|---|
Priority: | normal | Milestone: | R1/beta2 |
Component: | Applications/DiskUsage | Version: | R1/Development |
Keywords: | Cc: | ||
Blocked By: | Blocking: | ||
Platform: | All |
Description
This is hrev54083, 32bit.
When starting DiskUsage, only a grey window pops up, pegging one core. I had this for some time, but nobody else could reproduce. I finally found what's different for me: I got 7 partitions mounted. That, I guess, trips up DiskUsage when setting up the tabs for those volumes. This from the debug report:
0x71844830 0x2383b11 VolumeTab::IconWidth(VolumeTab) + 0xd ... 0x718448d0 0x23840bd ControlsView::VolumeTabView::TabFrame(ControlsView::VolumeTabView, int32) + 0x1c5 0x71844970 0x15e4b36 BTabView::DrawTabs() + 0x162 0x718449b0 0x15e4922 BTabView::Draw(BRect) + 0x32 0x718449f0 0x160cf3e BView::_Draw(BRect) + 0x92 0x71844bc0 0x1612350 BWindow::DispatchMessage(BMessage*, BHandler*) + 0xf04 0x71844c20 0x1616d04 BWindow::task_looper() + 0x2d0 0x71844c50 0x1528c99 BLooper::_task0_(void*) + 0x3d 0x71844c78 0xcbeccb thread_entry + 0x27 00000000 0x61638258 commpage_thread_exit + 0
After unmounting one of my partitions, the tabs of the remaining volumes fit in the DiskUsage default window size and it starts.
If I then increase the window size, the next time I launch DiskUsage with all 7 partitions mounted, they'll fit in the bigger window and DiskUsage launches OK.
Change History (4)
comment:1 by , 5 years ago
comment:3 by , 5 years ago
Assign tickets with status=closed and resolution=fixed within the R1/beta2 development window to the R1/beta2 Milestone
comment:4 by , 5 years ago
Milestone: | Unscheduled → R1/beta2 |
---|
Is this related: When slowly decreasing the window size, DiskUsage seizes up when the tab labels begin to be truncated, pegging a core with this debug report: