search

deltachat / deltachat-desktop

Email-based instant messaging for Desktop.
GNU General Public License v3.0
952 stars 170 forks source link

Selecting a chat resulted in blank screen #1091

Closed hpk42 closed 5 years ago

hpk42 commented 5 years ago

linux, desktop/core master from yesterday. can't really make sense of this traceback -- does it hint at what goes wrong? It might be that core-rust got stricter recently but still i'd like to see a code path that leads to the core-rust API call.

desktop-fail

Simon-Laux commented 5 years ago

no idea how you could get a rust trace from an error occurs in the javascript context, also this is the renderer process, that makes it even harder.

hpk42 commented 5 years ago

there is some sort of trace -- but it took me quite long to sort through the layers. am not that familiar with the code base, so had to rediscover that getMessage in desktop is basically dc_get_msg ... and that desktop relies on getting "empty messages" (i.e. message.id == 0 etc.) when calling dc_get_msg with a special id -- currently it's calling it with DAYMARKER (id=9) -- in https://github.com/deltachat/deltachat-core-rust/pull/771 i re-introduced dc_get_msg() to return an "empty" bogus message when asked for special id but really desktop shouldn't call dc_get_msg(1..9) but skip/ignore those. but i wasn't able to locate where this could be done :/

On Wed, Oct 30, 2019 at 11:05 -0700, Simon Laux wrote:

no idea how you could get a rust trace from an error occurs in the javascript context

-- You are receiving this because you authored the thread. Reply to this email directly or view it on GitHub: https://github.com/deltachat/deltachat-desktop/issues/1091#issuecomment-548041074