Opened 13 years ago

Closed 11 years ago

#752 closed bug (fixed)

[kernel] haiku could reboot if many apps opened at once

Reported by: diver Owned by: axeld
Priority: blocker Milestone: R1
Component: System/Kernel Version:
Keywords: Cc:
Blocked By: Blocking:
Has a Patch: no Platform: All

Description (last modified by axeld)

Tested under vmware with hrev18522 go to /boot/beos/apps or /boot/beos/preferences select all and press enter several times. The less memory you have the more a chance for reboot. If it will not reboot there's a good chance that some apps can't be closed, or some empty modal windows will stay onscreen until reboot.

Change History (6)

comment:1 Changed 13 years ago by diver

Summary: [kernel] haiku will reboot if many apps opened at once[kernel] haiku could reboot if many apps opened at once

comment:2 Changed 12 years ago by diver

Platform: All

Tested some more and more problems occured: sometimes i see something like "runtime_loader: cannot map image" or "out of memory" on a white screen, i think gdb couldn't be started, or just white screen without any message. Sometimes Deskbar and Tracker freeze... This bug don't let me test bug 757 more carefuly :-(

comment:3 Changed 12 years ago by diver

Oh and, very often after this reboot, haiku will not boot correctly (hang on haiku logo)

comment:4 Changed 12 years ago by diver

This is last messages from serial output:

intel_extreme: init_hardware() intel_extreme: init_hardware() failed: No such file or directory mga.driver: init_hardware() failed: General system error nm.driver: init_hardware() failed: General system error nv.driver: init_hardware() failed: General system error Radeon - init_hardware: Version: 5.1.0.1 Radeon - Radeon_CardDetect: no supported devices found radeon.driver: init_hardware() failed: General system error vesa: init_hardware() vesa: init_driver() vesa: publish_devices() vesa: find_device() loaded driver /boot/beos/system/add-ons/kernel/drivers/dev/graphics/vesa vesa: vesa_init() completed successfully! vesa: acc: vesa.accelerant

comment:5 Changed 12 years ago by diver

This is last messages from serial output before reboot:

vm_soft_fault: va 0x2efc not covered by area in address space

vm_page_fault: vm_soft_fault returned error -2147478783 on fault at 0x2efc, ip 0x5702cc, write 1, user 1, thread 0xf1

vm_page_fault: sending team "/boot/beos/apps/DeskCalc" 0xf1 SIGSEGV, ip 0x5702cc ("libroot.so_seg0ro" +0x212cc)

comment:6 Changed 11 years ago by axeld

Description: modified (diff)
Resolution: fixed
Status: newclosed

I'm closing this bug as the original problem has been fixed. If there are remaining bugs that fit the additional comments in this report, please open a new bug for them.

Note: See TracTickets for help on using tickets.