Opened 20 years ago
Closed 20 years ago
#1858 closed defect (fixed)
DIG: Starting new games takes a long time (regression)
| Reported by: | fingolfin | Owned by: | fingolfin |
|---|---|---|---|
| Priority: | high | Component: | Engine: SCUMM |
| Version: | Keywords: | ||
| Cc: | Game: | The Dig |
Description
I just noticed that with latest CVS, and also with ScummVM 0.7.0, starting a new game of The Dig, that is, typing: ./scummvm dig takes a very long time. More specifically, from the point the ScummVM window opens (with black content) until the intro movie of The Dig starts, 10-12 seconds pass. With 0.6.1b, the movie starts almost instantly.
Ticket imported from: #1091748. Ticket imported from: bugs/1858.
Change History (7)
comment:1 by , 20 years ago
comment:2 by , 20 years ago
| Owner: | set to |
|---|
comment:3 by , 20 years ago
i can't reproduce it. "Locking mutex IMuseDigital::callback() Unlocking mutex IMuseDigital::callback()" that is normal for whole game, callback 10 times per second.
comment:4 by , 20 years ago
Easily reproduceable here, though delay is about 8 seconds here, maybe due to faster computer. It loops in script 149 by that time, though. Processor load is 100%.
comment:5 by , 20 years ago
bug is introduced by patch fix to another bug :) http://cvs.sourceforge.net/viewcvs.py/scummvm/scummvm/scumm/debugger.cpp?r1=1.135&r2=1.136
comment:6 by , 20 years ago
| Owner: | changed from to |
|---|---|
| Resolution: | → fixed |
| Status: | new → closed |
I just run Dig with -x7, and noticed that during the "hang" we see a lot of
Locking mutex IMuseDigital::callback() Unlocking mutex IMuseDigital::callback() Locking mutex IMuseDigital::callback() Unlocking mutex IMuseDigital::callback() ...
Maybe this issue is related to iMuseDigital in some way? This is just a wild guess, I see no strong reason to believe it, but right now I can't think of anything... aquadran, maybe you have an idea?