Opened 18 years ago

Last modified 6 years ago

#511 closed bug

[ScreenSaver] Many stability and other problems — at Version 3

Reported by: diver Owned by: axeld
Priority: normal Milestone: R1
Component: Preferences/ScreenSaver Version: R1/Development
Keywords: Cc:
Blocked By: Blocking:
Platform: All

Description (last modified by jackburton)

I will attach my screensaver collection (115 items -2,4Mb) which i used for testing Haiku's ScreenSavers. Good news is that most of them (~100) seems to work, didn't test them in fullscreen mode though. Here are what i've found for the rest of them:

*1. I've started ScreenSaver from Terminal and on every ssaver selection i got

"runtime_loader: cannot open file /boot/beos/system/add-ons/Screen

Savers/<screensaver_name>".

Tip: open ~/config/settings window to delete screensaver_settings file when ScreenSaver start to crash on start. I think this is something to work out too.

*2. This screensavers will crash ScreenSaver pref: DS_Wobble: Segment violation KanjiSaver: Segment violation LicenseBreaker: Segment violation MeltdownBlur: Trying to delete a view that belongs to a window.Call RemoveSelf first. PrimalVision: Trying to delete a view that belongs to a window.Call RemoveSelf first. Roto_saver: elf_resolve_symbol: could not resolve symbol SetiSaver: Segment violation Sphere: Segment violation ZeroWing: addon_file ain't readable. darn! ChaoticLine: have some problems too, don't remember. Samhain: will freeze ScreenSaver. MapSaver: !!!Haiku will reboot!!! BrainWash: !!!Haiku will became black&white!!! IdleMind: ScreenSaver will close.

*3. Screensavers are wrongly sorted in the end of that list. *4. Almost all ssaver have font sensitive issues. (e.g. Nebula ;-) ) *5. ScreenSaver itself isn't font sensetive. *6. Running almost every screensaver in fullscreen will not let you out. You have to switch to another workspace and kill screen_blanker. (test case: Nebula) *7. After you killed screen_blanker in #6 via team monitor switch to first workspace, team monitor will be behind ScreenSaver pref. *8. If you have this savers installed and delete ScreenSaver_settings, after ScreenSaver start it will not select 1st module, but 6th or 7th instead. *9. Module listview need to prettfy.

All in all this is collection is a good stress tests for haiku, which should show it week sides. If there is a need, i could attach back traces for every crashing module.

Change History (6)

by diver, 18 years ago

Attachment: ScreenSaver_1.zip added

screensaver collection part 1

by diver, 18 years ago

Attachment: ScreenSaver_2.zip added

screensaver collection part 2

by diver, 18 years ago

Attachment: ScreenSaver_3.zip added

screensaver collection part 3 (last)

comment:1 by diver, 18 years ago

Platform: All

Some problems went away and some new problems appears. 80% of ssavers will not work without libnet.so, so i made up a link to libnetwork.so to make them work. Very often after screen_blanker crash, app_server will deadlock too. Sometimes when screensaver pref crashes and then you close debug window frozen screensaver will stay on screen until i kill gdb from processcontroller. If you select first ssaver and then hold down down arrow you will crash ScreenSaver.

All in all there is a big troubles with screensavers, so it would be nice if you could have a look at those, Axel!

comment:2 by diver, 18 years ago

If after screen_blanker crash you will quickly press ok in crash window app_server will not die!

comment:3 by jackburton, 17 years ago

Description: modified (diff)

Diver, can you recheck after hrev19891 ?

Note: See TracTickets for help on using tickets.