Custom Query (444 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (13 - 15 of 444)

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
Ticket Resolution Summary Owner Reporter
#347 fixed Crash bug due to recent Listtree changes Thore Böckelmann Oliver Roberts
Description

Summary

There seems to be a bug in the Listtree.mcc changes that you made regarding fixing the width to the longest tree item. It is causing IBrowse's hotlist manager window to crash if groups have been used in the hotlist.

It crashes with 21.14, but not 21.12. As it freezes the system on my A1XE, I can't get at the crashlog - maybe you can? I can send any relevant IBrowse code to you that the crashlog points to, if required. Occurs with IBrowse 2.4 and 2.5.

Steps to reproduce

If your hotlist has groups in it, it will crash when opening. If not, the best way to reproduce is to start with an empty hotlist and then click the "Add group" button which triggers an instant crash/freeze.

#431 fixed System freeze when dragging the address field in Odyssey 1.23 Gregor
Description

Summary

System freeze when dragging accidentally the address field in Odyssey 1.23. This can happen when trying to copy and paste text from/to the address field. The problem is also present in Odyssey 1.23-R5 beta01, 02, 03 and 04.

Steps to reproduce

  1. Move the mouse pointer to the leftmost end of the address field in Odyssey, so that the pointer still stays as a text pointer (vertical bar).
  2. Press the left mouse button and keep it down.
  3. Move the mouse toward right, until the pointer freezes.

Freeze is 100% reproducible in my system.

Expected results

Dragging the address field should not even be possible.

Actual results

The address field is dragged, after which the system freezes (mouse/keyboard do not react any more).

Regression

Hardware reset is needed.

Notes

Tested in AmigaOne X5000/20 with AmigaOS 4.1 Prerelease (resail version, no beta), max RAM amount.

#387 fixed Video memory trouble with R2 Thore Böckelmann K-L
Description

Summary

MUI 5-2018-R2 seems to eat a lot of video memory without freeing it.

Steps to reproduce

  1. Launch a monitor to check video memory consumption (to be done with R1 and then R2 to see differences)
  1. Launch any MUI application and check video memory consumption

Expected results

A huge amount of video memory will be used while using an MUI Application (Odyssey for example).

Actual results

More than 50% of video memory (I have 256MB here) will be used and not be freed when quitting all MUI applications.

Regression

It is a regression from R1.

Notes

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
Note: See TracQuery for help on using queries.