|
|
note also, logs are saved to %appdata%\Neos Eureka S.r.l\... instead of %appdata%\EurekaLab s.a.s\..... (it would be preferable if it didn't change the location of the logs in different versions of MM |
|
|
Fixed |
|
|
Still not Sent, but now I get this dialog |
|
|
bug17654.jpg (28,722 bytes) |
|
|
Fixed ... it was used old ecc compiler. |
|
|
Verified 2324 Sending is working OK. Have they received? NOTE: I still get 0017654:0062397 dialog, is it I wonder if it can be suppressed and normal dialog be shown? (Low priority for later versions maybe) |
|
|
1 When I try to use Help > Debug > Send logs with build 2324 ---> Dialog with 'User exception' message + [Send log] 2 Click [Send log] --> Dialog requesting additional info re. repro steps 3 Click [OK] --> Sending bug report: connecting to server and after a few seconds --> Can't execute command.... (see attached image) failed-crashlog-send.jpg (26,310 bytes) |
|
|
Fixed |
|
|
Performing Help > Debug > Send Logs is still problematic on 2325. 1) Log ID does not get copied to clipboard when the setting is checked (Also, it used to be checked by default but it is no longer checked by default). 2) After the log is sent, the interface usually freezes for 30 seconds before the "Restart/Continue" dialog appears.' 3) Occasionally, I get additional EurekaLog crash dialogs after closing MM. To reproduce: i. Send logs via Help>Debug>Send logs ii. Restart when the Restart/Continue dialog appears iii. After MM opens, close it with the X. iv. a EurekaLog crash dialog appears, which actually repeatedly reopens when I click OK. I've had to close it somewhere around 3-7 times before it closes for good. |
|
|
re 1) fixed |
|
|
While trying to fix Eureka code re the "Stack overflow" on handled exception ( 0017670 ) I found that: 4) starting MM5 built with Eureka is extremely slow, it takes more 5 seconds before the render process (MediaMonkeyEngine.exe) is started and splash screen hidden!! it starts within a second (or two) when not compiled with Eureka or with older builds (with older Eureka) 5) Performing Help > Debug > Send Logs => mine log did not come 6) Further issues observed by user frank1969a : https://www.mediamonkey.com/forum/viewtopic.php?f=30&t=98637 -- mainly logs 2338EEBD, 51A3812D Investigating further, but seeing the number of issues with the new Eureka log version it makes sense to revert to an older version for now |
|
|
4&5) are resolved, it was caused by old ecc32.exe in RAD's bin folder 6) it was shown that the remaining issue is unrelated to the new Eureka, tracking it as 0017677 (details there) |
|
|
7) Currently the new Eureka does not catch alerts in JS code. e.g. add alert('bla bla'); to JS code somewhere: => message dialog with 'bla bla' is shown, but Eureka dialog (to send logs) isn't shown. With the old Eureka it shown the 'Send logs' on alerts |
|
|
FYI 3) seems to occur less often on 2326 somehow, but it still occurs some of the time. I sent logs 3 times and the EurekaLog crash dialog only showed up on the third time. |
|
|
7) in addition any JS exception is not caught by Eureka now! Tried to add window.blabla.blab2 = false; to window.uitools.showOptions and upon trying to open Options dialog just this was shown: https://www.dropbox.com/s/w9s91ze50mzr8p8/screenshot%202021-03-22%2016.10.28.png?dl=0 i.e. no Eureka dialog! |
|
|
7) fixed |
|
|
7) Confirmed the fix on current SVN sources |
|
|
Fixed |
|
|
8) It's not possible to test most of the fixes because every attempt to use Help > Debug > Send Logs results in MM freezing and eventually generating crashlog A58F50A3 See: https://www.screencast.com/t/0klYbe6oPHCy 9) The 'Send logs' dialog seems to have text that is cut off (look at the bottom border of the dialog in the video). |
|
|
Fixed |
|
|
Verified in 2328: 1) Log ID gets copied 2) The restart/continue dialog appears soon after the log is submitted 6) Was fixed at 0017677 crashes haven't been observed in several builds. 7) JS Exceptions now caught. Confirmed by Ludek 8) Help > Debug > Send logs always crashes. Verified fix. 9) Send logs dialog displays incorrectly. Verified fix. Still to test: 5) Need to confirm that logs are actually sent Remaining open issues: 3) a) Eurekalog still crashes after 'Restart' and then 'Close' at the 'Restart in safe mode' prompt. See original repro steps reported by Ludek. Logs attached. b) When the crashlog is sent, the 'Provide additional details' dialog appears and then disappears without waiting for the user to enter info. Is this intentional (and if so, the dialog shouldn't appear)? Note I think it's preferable to ask the user for this info. c) When MM restarts, the following dialog appears 'Media servner 'MediaMonkey Library' could not start: port 10894 is already in use....'. This implies that MM didn't fully terminate before restarting! 10) New issue. Submitting a crashlog with no text in the additional info dialog --> MM whitescreen 1 Run MM 2 Help > Debug > Send logs, then [Send log] -->Additional info: 3 Don't enter anything, click [OK] --> White screen sometimes occurs at this point. If not, 'Restart in Safe mode?' dialog appears 4 [Continue] 5 Help > Debug > Send logs, then [Send log] --> White Screen! |
|
|
5) received ~10 bugreports from you 3b) 'provide additional info' dialog appears always before log is sent (at least for me) 10) fixed |
|
|
11) Upon clicking Menu > Debug > Send logs --> the menu becomes disconnected from MM5 (i.e. always stays on top independently of the MM app). e.g. 1 Click Menu > Debug > Send logs --> UI seems to freeze until the Send logs dialog appears 2 Click MM in the taskbar --> The MM menu stays on top, and the MM App is non-responsive. What should happen is that as soon as the user clicks Send logs, the menu should close. |
|
|
Re-opening issue 2) 'Restart dialog' seems to be taking 20s to appear Issues 3 a) /c) are no longer replicable. i.e. no crashes on restart and no warning re. the UPnP server Port. |
|
|
11) fixed in 2330 |
|
|
Just testing and I can confirm 11) is fixed on current SVN sources. Re item 2) I can confirm the issue and actually takes more than 30 seconds for me until the restart / continue dialog appears. This hasn't been the case with the old Eureka. |
|
|
Verified issue 11) in build 2330. Only item 2 remains. |
|
|
12) The new Eureka log does not include JS callstack in case of JS exception! Tested issue 0017719 (before the fix) and - with build 2330 the JS callstack isn't included, see log ID 14D1FC2F - with build 2232 (old Eureka) the JS callstack is included, see log ID A04C0AC8 Moving target back to 5.0 because of issue 12) as including JS callstack is important for us to analyze the logs. |
|
|
Item 12) fixed in 2332 |
|
|
Currently MM5 often does not show the "Submit logs" dialog and ends with "white screen" even if MediaMonkeyEngine.el was correctly generated (e.g. issue 0017979 ) As discussed via IM : MM5 should be able to detect this situation on the next start and show something like "MediaMonkey crashed the last time it was running and hasn't been able to send crash report, would you like to submit it now?" -- or submit the crash report automatically on the next MM start. |
|
|
I'd suggest something that retains the current workflow so that users always take the same approach re. crashes. e.g.: MediaMonkey terminated unexpectedly when last run. [[Send logs...]] [Cancel] Click 'Send logs' --> Eurekalog dialog appears (same as usual) |
|
|
FYI: Eureka does not show the "Submit logs" dialog on some exceptions like those from issues 0018028 or 0018006 It shows just "Application error" dialog with [Restart] [Restart in safe mode] [Continue] buttons. |
|
|
13) Using menu Debug > Send logs ends up with unresponsive MM window that needs to be killed via task manager: image-2.png (42,770 bytes) |
|
|
And several leftovers remains: image-3.png (13,579 bytes) |
|
|
Changed target back to 5.0.3 for the item 13) which makes MM unusable after a crash (or Send logs) and is hard to kill (as various MM sub-precesses remains) Note that MM5 freezes _after_ the logs has been submited (this differs from item 11). MM5 should either self-restart and kill the leftovers -- or somehow gracefully go from this "locked" situation. |
|
|
Barry is now reporting item 13) as 0018944 -- so it can be fixed there |
|
|
The issue has been fixed in 2615 as 0018944 |
|
|
Verified 2616 |
- Anonymous
